Methods and apparatus for increasing the efficiency of electronic data storage and transmission

ABSTRACT

An electronic data storage and transmission system. A plurality of electronic data objects may be associated to a plurality of electronic data indicators, and the associations may be combined. Contextual awareness of a second location may allow generation of streamlined electronic data objects. Electronic spatial data objects may be automatically contiguously combined and compression may be leveraged with combination efficiencies. Combinations of electronic data objects may be threshold limited. Transmission of electronic data may achieve effective compression and effective transmission rates exceeding a benchmark network transmission rate of an electronic data communications network.

BACKGROUND

The present inventive technology relates to the field of electronic datastorage and transmission. The present inventive technology may be usedmore particularly, but not exclusively, to supplement or replaceconventional electronic data compression technologies to achieveimproved efficiencies in such electronic data storage and transmission.

Compression technologies are widely employed in the field of electronicdata storage and transmission to increase the efficiencies of suchstorage and transmission. The benefits of compression are well known,and many conventional approaches to the compression of electronic dataexist. However, compression technologies may fail to address some of theprincipal causes of inefficiencies in electronic data storage andtransmission.

For example, electronic data may tend to exist in a widely dispersednature. In an electronic communications network, electronic data mayexist at different nodes or termini of the network. On a computingdevice, electronic data may be stored in disparate locations in computermemory. In one conventional technology, a client may be required to makemultiple requests of a server to load a World Wide Web page, in as muchas the electronic data required by the client to load the page may belocated at disparate locations on the server. For example, a clienttypically may require multiple CSS, script, and image files from theserver to load the page. If these files are located at differentlocations on the server, as typically may be the case, the client may berequired to make a separate request for every separate location at whichthe necessary electronic data may be found, leading to inefficienciesthat conventional compression technologies do not address.

In addition, compression technologies often may modify the conventionalinfrastructure of modern electronic data storage and transmissiontechnologies. For example, compression technologies may often act toalter basic infrastructure elements such as the TCP, IP, or HTTP layersof Internet and World Wide Web electronic data transmission.Implementing these alterations may require an expenditure of resources,such as perhaps the time and costs associated with developing,installing, and maintaining the software and hardware elements, and itmay be inherently undesirable to alter the underlying infrastructure ofelectronic data storage and transmission. Conventional compressiontechnologies accordingly may not be well suited to utilizing suchconventional infrastructure it its most efficient manner.

Compression technologies also may not take full advantage of electronicautomation. For example, certain kinds of electronic data amalgamation,such as the creation of image sprites or the limiting of theaccumulation of dynamically generated content on World Wide Web pages,may conventionally have required significant human action,implementation, or supervision.

It also may be the case that compression technologies may notconventionally be leveraged to their fullest effect. For example, imagecompression schemes such as JPG, GIF, or PNG may only act to compress anindividual image file, and may not be leveraged to take advantage ofadditional compression possibilities across multiple compressed imagefiles.

In addition, compression technologies may be context unaware. Forexample, in compressing electronic data to improve the efficiency oftransmission, conventional compression may only be able to compress suchdata in its entirety or not at all, and may not be able to distinguishthose portions of the electronic data having an actual use at thereceiving end from those portions of the electronic data that may gounused at the receiving end.

The foregoing problems related to conventional compression technologiesmay represent a long-felt need for an effective solution to the same.While implementing elements may have been available, actual attempts tomeet this need may have been lacking to some degree. This may have beendue to a failure of those having ordinary skill in the art to fullyappreciate or understand the nature of the problems and challengesinvolved. As a result of this lack of understanding, attempts to meetthese long-felt needs may have failed to effectively solve one or moreof the problems or challenges here identified. These attempts may evenhave led away from the technical directions taken by the presentinventive technology and may even result in the achievements of thepresent inventive technology being considered to some degree anunexpected result of the approach taken by some in the field.

SUMMARY OF THE INVENTION

In one embodiment, an object of the inventive technology is to provide amethod for consolidating input/output of electronic data transmissioncomprising the steps of: storing multiple electronic data objects at afirst location; storing multiple electronic data indicators at a secondlocation; linking said first location and said second location with aninput/output pathway; associating a plurality of said multipleelectronic data objects at said first location to a plurality of saidmultiple electronic data indicators at said second location through saidinput/output pathway to create multiple electronic data associations;consolidating at least some of said multiple electronic dataassociations into a single consolidated electronic data association; andtransmitting electronic data through said input/output pathway utilizingsaid single consolidated electronic data association.

In another embodiment, an object of the inventive technology is toprovide an input/output electronic data transmission consolidationapparatus comprising: a first electronic storage medium having multipleelectronic data objects stored thereon; a second electronic storagemedium having multiple electronic data indicators stored thereon; aninput/output pathway linking said first electronic storage medium andsaid second electronic storage medium; an electronic data associator towhich said first electronic storage medium having multiple electronicdata objects stored thereon, said second electronic storage mediumhaving multiple electronic data indicators stored thereon, and saidinput/output pathway linking said first electronic storage medium andsaid second electronic storage medium are responsive; an electronic dataconsolidator responsive to said electronic data associator and to whichsaid input/output pathway linking said first electronic storage mediumand said second electronic storage medium is responsive; and anelectronic data transmitter responsive to said electronic dataconsolidator and to which said input/output pathway linking said firstelectronic storage medium and said second electronic storage medium isresponsive.

In another embodiment, an object of the inventive technology is toprovide a method for effectively compressing electronic datatransmission comprising the steps of: storing multiple electronic dataobjects at a first location; storing multiple electronic data indicatorsat a second location; combining said multiple electronic data objectsinto a single combined electronic data object at said first location;combining said multiple electronic data indicators into a singlecombined electronic data indicator at said second location; associatingsaid single combined electronic data object at said first location tosaid single combined electronic data indicator at said second location;effectively compressing at least one request from said second locationfor at least one said electronic data object at said first location withsaid single combined electronic data indicator at said second location;and effectively compressing provision from said first location of atleast one said electronic data object to said second location with saidsingle combined electronic data object at said first location.

In another embodiment, an object of the inventive technology is toprovide an electronic data transmission effective compression apparatuscomprising: a first electronic storage medium having multiple electronicdata objects stored thereon; a second electronic storage medium havingmultiple electronic data indicators stored thereon; an electronic dataobject combiner to which said first electronic storage medium havingmultiple electronic data objects stored thereon is responsive; anelectronic data indicator combiner to which said second electronicstorage medium having multiple electronic data indicators stored thereonis responsive; an electronic data associator responsive to saidelectronic data object combiner and said electronic data indicatorcombiner; and an electronic data object request and provide effectivecompressor responsive to said electronic data associator and to whichsaid first electronic storage medium having multiple electronic dataobjects stored thereon and said second electronic storage medium havingmultiple electronic data indicators stored thereon are responsive.

In another embodiment, an object of the inventive technology is toprovide a method for increasing the effective rate of transmittingelectronic data comprising the steps of: storing an electronic dataobject at a first location; linking said first location to a secondlocation via an electronic data communications network; accessing saidelectronic data communications network utilizing an electronic messageassembly protocol and an electronic message addressing protocol; havinga benchmark network transmission rate for electronic data transmissionvia said electronic data communications network utilizing saidelectronic message assembly protocol and said electronic messageaddressing protocol; transmitting said electronic data object from saidfirst location to said second location via said electronic datacommunications network at an effective network transmission rate greaterthan said benchmark network transmission rate.

In another embodiment, an object of the inventive technology is toprovide an electronic data transmission effective rate augmentationapparatus comprising: a first electronic storage medium having anelectronic data object stored thereon; an electronic data communicationsnetwork linking said first electronic storage medium to a secondelectronic storage medium; an access point to said electronic datacommunications network responsive to an electronic message assemblyprotocol and an electronic message addressing protocol; a benchmarknetwork transmission rate of said electronic data communications networkresponsive to said electronic message assembly protocol and saidelectronic message addressing protocol; an electronic data objecttransmission effective rate augmenter responsive to said benchmarknetwork transmission rate and to which said first electronic storagemedium having an electronic data object stored thereon, said secondelectronic storage medium, and said electronic data communicationsnetwork linking said first electronic storage medium to said secondelectronic storage medium are responsive.

In another embodiment, an object of the inventive technology is toprovide a method for combining electronic spatial data comprising thesteps of: automatically accessing multiple electronic spatial dataobjects; automatically identifying at least one characteristic of eachsaid electronic spatial data object relevant to contiguous combinationof said multiple electronic spatial data objects; automaticallyaggregating said multiple electronic spatial data objects having said atleast one automatically identified characteristic relevant to saidcontiguous combination of said multiple electronic spatial data objects;automatically contiguously combining said multiple electronic spatialdata objects using each said automatically identified characteristic;creating a single contiguously combined electronic spatial data object.

In another embodiment, an object of the inventive technology is toprovide an electronic spatial data combination apparatus comprising:multiple electronic spatial data objects stored on at least oneelectronic storage medium; an automated electronic spatial data objectaccessor responsive to said multiple electronic spatial data objects; anautomated contiguous combination characteristic identifier responsive tosaid automated electronic spatial data object accessor; an automatedelectronic spatial data object aggregator responsive to said automatedcontiguous combination characteristic identifier; an automatedelectronic spatial data object contiguous combiner responsive to saidautomated electronic spatial data object aggregator; an automated singlecontiguously combined electronic spatial data object creator responsiveto said automated electronic spatial data object contiguous combiner.

In another embodiment, an object of the inventive technology is toprovide a method for threshold combining electronic data comprising thesteps of: automatically accessing multiple electronic data objects;automatically identifying at least one characteristic of each saidelectronic data object relevant to a threshold criterion for combiningsaid multiple electronic data objects; automatically aggregating saidmultiple electronic data objects having said at least one automaticallyidentified characteristic relevant to said threshold criterion forcombining said multiple electronic data objects; automaticallydetermining if said threshold criterion for combining said multipleelectronic data objects has been satisfied; automatically combining saidmultiple electronic data objects in accordance with said automaticdetermination if said threshold criterion for combining said multipleelectronic data objects has been satisfied.

In another embodiment, an object of the inventive technology is toprovide an electronic data threshold combination apparatus comprising:multiple electronic data objects stored on at least one electronicstorage medium; an automated electronic data object accessor responsiveto said multiple electronic data objects; an automated thresholdcriterion combination characteristic identifier responsive to saidautomated electronic data object accessor; an automated electronic dataobject aggregator responsive to said automated threshold criterioncombination characteristic identifier; an automated threshold criteriondeterminer responsive to said automated electronic data objectaggregator; an automated electronic data object combiner responsive tosaid automated threshold criterion determiner.

In another embodiment, an object of the inventive technology is toprovide a method for compressing electronic spatial data comprising thesteps of: accessing multiple electronic spatial data objects;aggregating said multiple electronic spatial data objects for combiningsaid multiple electronic spatial data objects; combining said multipleelectronic spatial data objects; creating a single combined electronicspatial data object; electronically compressing said single combinedelectronic spatial data object to create an electronically compressedcombined electronic spatial data object.

In another embodiment, an object of the inventive technology is toprovide an electronic spatial data compression apparatus comprising:multiple electronic spatial data objects stored on at least oneelectronic storage medium; an electronic spatial data object accessorresponsive to said multiple electronic spatial data objects; anelectronic spatial data object aggregator responsive to said electronicspatial data object accessor; an electronic spatial data object combinerresponsive to said electronic spatial data object aggregator; a singlecombined electronic spatial data object creator responsive to saidelectronic spatial data object combiner; a combined electronic spatialdata object electronic compressor responsive to said single combinedelectronic spatial data object creator.

In another embodiment, an object of the inventive technology is toprovide a method for transmitting streamlined electronic data comprisingthe steps of: storing an electronic data object at a first location;automatically recognizing a use for said electronic data object at asecond location; automatically determining constituent parts of saidelectronic data object necessary for said use at said second locationand constituent parts of said electronic data object unnecessary forsaid use at said second location; automatically selectively removingsaid constituent parts of said electronic data object unnecessary forsaid use at said second location to create a streamlined electronic dataobject; electronically transmitting said streamlined electronic dataobject from said first location to said second location.

In another embodiment, an object of the inventive technology is toprovide a streamlined electronic data transmission apparatus comprising:a first electronic storage medium having an electronic data objectstored thereon; an automated second location electronic data object userecognizer responsive to said electronic data object; an automatedelectronic data object second location use constituent part determinerresponsive to said automated second location electronic data object userecognizer; an automated electronic data object second locationdispensable constituent part determiner responsive to said automatedsecond location electronic data object use recognizer; an automatedstreamlined electronic data object creator responsive to said automatedelectronic data object second location use constituent part determinerand said automated electronic data object second location dispensableconstituent part determiner; an automated streamlined electronic dataobject transmitter responsive to said automated streamlined electronicdata object creator.

Naturally, further objects of the inventive technology will becomeapparent from the description and drawings below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic representation of an input/output electronic datatransmission consolidation apparatus in one exemplary embodiment.

FIG. 2 is a schematic representation of an electronic data transmissioneffective compression apparatus in one exemplary embodiment.

FIG. 3 is a schematic representation of an electronic data transmissioneffective rate augmentation apparatus in one exemplary embodiment.

FIG. 4 is a schematic representation of an electronic spatial datacombination apparatus in one exemplary embodiment.

FIG. 5 is a schematic representation of an electronic data thresholdcombination apparatus in one exemplary embodiment.

FIG. 6 is a schematic representation of an electronic spatial datacompression apparatus in one exemplary embodiment.

FIG. 7 is a schematic representation of a streamlined electronic datatransmission apparatus in one exemplary embodiment.

FIG. 8 is a schematic representation of a one-sided self-containedelectronic data exchange transaction implementation architecture in oneexemplary embodiment.

FIG. 9 is a schematic representation of a combined pointer apparatus inone exemplary embodiment.

FIG. 10 is a schematic representation of a combined file apparatus inone exemplary embodiment.

FIG. 11 is a schematic representation of a redundant executable scripteliminator apparatus in one exemplary embodiment.

FIG. 12 is a schematic representation of a transmission overhead reducerapparatus in one exemplary embodiment.

FIG. 13 is a schematic representation of an electronic communicationsnetwork addition in one exemplary embodiment.

FIG. 14 is a schematic representation of an automated programming codeminifier in one exemplary embodiment.

FIG. 15 is a schematic representation of a combiner programming codeexecution processor in one exemplary embodiment.

FIG. 16 is a table presenting effective compression data for electronicdata comprising CSS data, script data, and image data in one exemplaryembodiment.

FIG. 17 is a table presenting effective compression data for electronicdata comprising CSS data in one exemplary embodiment.

FIG. 18 is a table presenting effective compression data for electronicdata comprising script data in one exemplary embodiment.

FIG. 19 is a table presenting effective compression data for electronicdata comprising image data in one exemplary embodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present inventive technology includes a variety of aspects, whichmay be combined in different ways. The following descriptions areprovided to list elements and describe some of the embodiments of thepresent inventive technology. These elements are listed with initialembodiments, however it should be understood that they may be combinedin any manner and in any number to create additional embodiments. Thevariously described examples and preferred embodiments should not beconstrued to limit the present inventive technology to only theexplicitly described systems, techniques, and applications. Further,this description should be understood to support and encompassdescriptions and claims of all the various embodiments, systems,techniques, methods, devices, and applications with any number of thedisclosed elements, with each element alone, and also with any and allvarious permutations and combinations of all elements in this or anysubsequent application.

In various embodiments, the inventive technology may utilize one or moreelectronic data objects. Electronic data objects may be understood toinclude electronic entities that can be manipulated by the commands of aprogramming language, such as a value, variable, function, data element,or data structure. An electronic data object also may compriseprogramming code, such HTML or other kinds of programming code. Examplesof electronic data objects may include files, Web pages, scripts, CSS,or image information. A file generally may be understood to include acollection of related electronic data or programming code stored on anelectronic storage medium.

Various embodiments of the inventive technology also may utilize one ormore electronic data indicators. Electronic data indicators may beunderstood to include electronic entities that can indicate locationinformation for an electronic data object. For example, an electronicdata indicator may have address information for one or more electronicdata objects, such as an address to a location in electronic memory, anaddress to a location on an electronic communications network, or thelike.

An example of an electronic data indicator in one embodiment may be apointer on a Web page. For example, in conventional World Wide Webarchitecture, a client may request information from a server to load aWeb page. The server may respond with information for the Web page,wherein the information may include one or more pointers for the clientto follow in order to retrieve information for the Web page. In someexamples, the pointers may direct the client to obtain CSS information,script information, image information, or other kinds of informationnecessary for the Web page, wherein such information may be storedelsewhere.

Now with reference primarily to FIG. 1, embodiments of the inventivetechnology may involve a method for consolidating input/output ofelectronic data transmission and an input/output electronic datatransmission apparatus.

The method may involve storing multiple electronic data objects (102) ata first location, such as with a first electronic storage medium (101),and storing multiple electronic data indicators (104) at a secondlocation, such as a second electronic storage medium (103).

As used herein throughout, such locations may be any suitable locationsat which electronic data may be stored. Examples of such locations maybe network nodes or locations within a computing device, such ascomputer memory. In some embodiments, a first location may be a serverand a second location may be a client. Embodiments also may involve oneor more such locations being a mobile computing device.

The inventive technology may involve linking the first location and thesecond location with an input/output pathway (105). Such an input/outputpathway (105) may allow electronic data to be moved relative to thefirst location and the second location, such as by movements includingin-and-out, two-way, back-and-forth, send-and-receive, and the like.Naturally, input/output may involve either input, output, or both.

In some embodiments, an input/output pathway (105) may be an electroniccommunications network. Such networks may allow transmission ofelectronic data from at least one location to at least another location,and may include wired or wireless, analog or digital, and hardware andsoftware elements. Examples of electronic communications networks mayinclude the Internet and the World Wide Web, but also may include, forexample, internal buses or other architectures within an individualcomputing device.

The inventive technology may involve associating a plurality of multipleelectronic data objects (102) at a first location to a plurality of saidmultiple electronic data indicators (104) at a second location throughan input/output pathway (105) to create multiple electronic dataassociations. Such electronic data associations may serve to connect orotherwise bring into relation such electronic data objects (102) andelectronic data indicators (104). For example, one kind of electronicdata association may be a pointer at a client pointing to a file, suchas a CSS, script, or image file, at a server. Embodiments may involveone-to-one electronic data associations, such as one pointer pointing toone such file, or perhaps more generally such as creating at least onecounterpart electronic data object (102) and electronic data indicator(103). Accordingly, embodiments may include an electronic dataassociator (106) to which said first electronic storage medium (101),said second electronic storage medium (103), and said input/outputpathway (105) are responsive, and perhaps may include an electronic dataobject and electronic data indicator counterpart architecture (119).

In some embodiments, associating may involve creating mutuallyinterdependent functionality among a plurality of multiple electronicdata objects (102) at a first location and a plurality of a multipleelectronic data indicators (104) at a second location. In this kind ofarrangement, the object and the indicator may each be necessary forcreating the functional utility of the association by being mutuallyinterdependent on one another. Accordingly, embodiments may involve amutually interdependent functionality architecture (123).

For example, creating a mutually interdependent functionality mayinvolve addressing at least one electronic data indicator (104) at asecond location (103) to at least one electronic data object (102) at afirst location (101) and delivering the electronic data object (102)from the first location (101). In the case of a pointer at a clientpointing to a file, such as a CSS, script, or image file, at a server,the functional utility of the association may derive from therelationship between the pointer pointing to a file and the file beingpointed, such as to allow a client to follow the pointer to access thefile, and a server to deliver the file to the client. Accordingly,embodiments may include an electronic data indicator address processor(109) and an electronic data object delivery processor (110).

In some embodiments, addressing may involve generating a charactersequence that uniquely identifies an electronic data object (102) andusing the character sequence to address the electronic data indicator(103) to the electronic data object (102). Accordingly, embodiment mayinvolve using a unique character sequence identification generator (111)responsive to an electronic data object (102) and an electronic dataindicator addresser (112) responsive to the unique character sequenceidentification generator (111). Delivering the electronic data object(102) may involve recognizing the character sequence used to address theelectronic data indicator (104) to the electronic data object (102), andmay involve retrieving the electronic data object (102) related to thecharacter sequence and delivering the electronic data object (102), suchas from a server to a client. Accordingly, embodiments may involve aunique character sequence identification recognizer (113) responsive toan addressed electronic data indicator (104), a unique charactersequence identification retriever (114) responsive to the uniquecharacter sequence identification recognizer (113), and an electronicdata object delivery system (115).

Moreover, the inventive technology may involve requesting an electronicdata object (102) using the character sequence in an initial request andavoiding repeating requests for the electronic data object (102) usingthe character sequence in subsequent requests. Accordingly, embodimentsmay include an electronic data object character sequence initial requestprocessor (116) and an electronic data object subsequent repeatedrequest avoidance processor (117). This may serve, for example, toreduce the number of requests or eliminate repeated requests for theelectronic data object, such as by client to a server, even if thecharacter sequence is presented in subsequent requests. Using thecharacter sequence in an initial request and avoiding repeating requestsmay be accomplished, for example, by providing appropriate instructionfrom one location to another location, such as from a server to aclient, perhaps in a server response to an initial request from aclient, and wherein the character sequence may be utilized to facilitatesuch instruction. Accordingly, embodiments may include a one locationinstruction architecture (118).

The inventive technology may involve consolidating at least somemultiple electronic data associations into a single consolidatedelectronic data association. Consolidating should be understood toinclude reducing multiple instances of electronic data associations intofewer instances of electronic data associations, in some cases perhapseven reducing to one single consolidated data association. Accordingly,embodiments may include an electronic data consolidator (107) responsiveto an electronic data associator (106) and to which an input/outputpathway (105) are responsive.

For example, in some embodiments consolidating may involve combining atleast some multiple electronic data associations into a singleconsolidated electronic data association. Accordingly, embodiments mayinclude an electronic data combiner (120).

In another example, consolidating may involve reducing the number oflocations of electronic data objects (102) and electronic dataindicators (102). Electronic data objects (102) stored at differentlocations may be consolidated into storage at one location, andelectronic data indicators (104) formerly indicating different locationsmay be consolidated into fewer indicators corresponding to the commonlocation of formerly disparate object locations. In this manner, whereindisparately located electronic data objects (102) formerly may haverequired multiple electronic data associations to accommodate thedisparate locations, the act reducing the number of locations ofelectronic data objects (102) and electronic data indicators (104) mayresult in consolidating the number of multiple electronic dataassociations. Accordingly, embodiments may involve an electronic dataobject location number reduction system and an electronic data indicatorlocation number reduction system.

More particularly, in some embodiments, consolidating may involvereducing the number of locations of css information, script information,and image information, such that such css information may beconsolidated at one location, such script information may beconsolidated at one location, and such image information may beconsolidated at one location. In this manner, wherein multiple css,script, and image pointers may have been required before consolidation,only a single css, script, and image pointer may be required afterconsolidation, again perhaps demonstrating how multiple css, script, andimage associations can be consolidated into fewer or even single css,script, image associations.

Of course, such acts of consolidation may involve reducing the number ofaccess events of multiple electronic data associations and may involvereducing the time to access electronic data objects (102). Access eventsmay be understood to involve the steps required in any individualassociation to utilize the associated functionality, such as byfollowing a pointer to an object and retrieving the object. Accordingly,embodiments may involve a multiple electronic data association accessevent reduction system (121). Naturally, wherein associations areconsolidated, the number of access events required and the timeassociated to implement them may be reduced. Accordingly, embodimentsmay include an electronic data object access time reduction system andan electronic data indicator access time reduction system.

The inventive technology may involve retaining a separately usablefunctionality of each individual electronic data association. This is tosay that notwithstanding any act of consolidation, the preexistingfunctionality of any individual association may be preserved. Forexample, wherein consolidating may involve creating consolidatedassociations for CSS, script, or image information, the consolidatedassociation still may be usable and may permit any individual css,script, or image information to be accessed and utilized from within theconsolidated CSS, script, or image information. Accordingly, embodimentsmay involve an individual electronic data association separate usefunctionality retention processor (122).

Naturally, consolidating multiple electronic data associations into asingle consolidated electronic data association may reduce the size ofsuch data associations. Embodiments may involve consolidating at leastsome of said multiple electronic data associations into a singleconsolidated electronic data association having a size of up to 52.3%less than the size of said unconsolidated multiple electronic dataassociations, consolidating CSS data associations into a singleconsolidated CSS data association having a size of up to 35.5% less thanthe size of unconsolidated multiple CSS data associations, consolidatingmultiple script data associations into a single consolidated script dataassociation having a size of up to 16.9% less than the size ofunconsolidated multiple script data associations, and consolidatingmultiple image data associations into a single consolidated image dataassociation having a size of up to 34.8% less than the size ofunconsolidated multiple image data associations. Accordingly,embodiments may include an up to 52.3% consolidation electronic dataconsolidator, an up to 35.5% consolidation CSS data consolidator, an upto 16.9% consolidation script data consolidator, and an up to 34.8%image data consolidator.

The inventive technology may involve transmitting electronic datathrough the input/output pathway (105) utilizing a single consolidatedelectronic data association. For example, the functionality created bythe association may form the basis of transmitting an electronic dataobject (102) using an electronic data indicator (104) from one locationto another, such as where a CSS file, script file, or image file may betransmitted from a server to client based on the relationship of apointer at the client to the location of the file on the server.Accordingly, embodiments may involve an electronic data transmitter(108) responsive to an electronic data consolidator (107) and to whichan input/output pathway (105) may be responsive.

In some embodiments, transmitting may involve selectively transmitting.In such cases, an electronic data transmitter (108) may be a selectiveelectronic data transmitter. For example, while a single consolidatedelectronic data association may have information related to multipleelectronic data objects (102) and multiple electronic data indicators(102), transmitting may involve using the single consolidated electronicdata association to transmit perhaps fewer than all of such objectsusing perhaps fewer than all of such indicators. In some embodiments,selectively transmitting may involve separately transmitting oneelectronic data object (102) using one electronic data indicator (104)of a single consolidated electronic data association, while otherembodiments may involve transmitting multiple electronic data objects(102) using multiple electronic data indicators (104) of a singleconsolidated electronic data association. In this manner, selectivelytransmitting may involve transmitting a single CSS object, scriptobject, or image object using a single pointer, even wherein multipleCSS objects, script objects, or image objects may have been consolidatedwith multiple pointers into a single consolidated electronic dataassociation.

Accordingly, embodiments may involve a separate electronic data objectand separate electronic data indicator transmission architecture (124),a transmission architecture (125) responsive to an electronic dataconsolidator (107), and a multiple electronic data object and multipleelectronic data indicator transmission architecture (126) responsive toan electronic data consolidator (107).

The act of selectively transmitting may be effected in variousembodiments by utilizing HTTP headers, such as wherein the informationof a single consolidated electronic data association may be carried byHTTP headers in request and response communications between a server anda client. For example, the consolidated electronic data associationinformation carried by an HTTP header may be used to select electronicdata. Accordingly, embodiments may include an HTTP header electronicdata selection processor responsive to an electronic data consolidator(107).

Transmitting electronic data in various embodiments also may involvetransmitting via one electronic data exchange transaction. For example,without the consolidation of multiple electronic data associations asdescribed herein, multiple electronic data exchange transactions may berequired to make use of electronic data objects (104) stored atdifferent locations. Via consolidation, a single electronic dataexchanged transaction may suffice to make use of such multipleelectronic data objects (104), such as wherein a single consolidatedelectronic data association may allow one pointer to access multiple CSSfiles, script files, or image files. In this manner, embodiments mayinvolve transmitting multiple electronic data objects (102) usingmultiple electronic data indicators (104) and avoiding multipleelectronic data exchange transactions. Accordingly, embodiments mayinvolve a single electronic data exchange transaction system and amultiple electronic data exchange transaction avoidance system (127) towhich said multiple electronic data objects (102) and said multipleelectronic data indicators (104) are responsive.

Of course, transmitting electronic data using these consolidationprinciples may involve transmitting fewer bytes of electronic data.Embodiments may involve transmitting up to 52.3% fewer bytes ofelectronic data through said input/output pathway utilizing said singleconsolidated electronic data association as compared to not utilizingsaid single consolidated electronic data association, transmitting up to35.5% fewer bytes of CSS data through said input/output pathwayutilizing said single consolidated electronic data association ascompared to not utilizing said single consolidated electronic dataassociation, transmitting up to 16.9% fewer bytes of script data throughsaid input/output pathway utilizing said single consolidated electronicdata association as compared to not utilizing said single consolidatedelectronic data association, and transmitting up to 34.8% fewer bytes ofimage data through said input/output pathway utilizing said singleconsolidated electronic data association as compared to not utilizingsaid single consolidated electronic data association. Accordingly,embodiments may include an up to 52.3% reduced bytes electronic datatransmitter, an up to 35.5% reduced CSS bytes electronic datatransmitter, an up to 16.9% reduced script bytes electronic datatransmitter, and an up to 34.8% reduced image bytes electronic datatransmitter.

Now with reference primarily to FIG. 2, embodiments of the inventivetechnology may involve a method for effectively compressing electronicdata transmission and an electronic data transmission effectivecompression apparatus.

The method may involve storing multiple electronic data objects (202) ata first location, such as on a first electronic storage medium (201),and multiple electronic data indicators (222) at a second location, suchas on a second electronic storage medium (221), perhaps as may have beendescribed elsewhere herein. Embodiments also may involve transmittingelectronic data from said first location to said second location, suchas with an electronic data transmitter (223).

Embodiments may involve combining the multiple electronic data objects(102) into a single combined electronic data object at the firstlocation (101), and combining the multiple electronic data indicators(222) into a single combined electronic indicator at the second location(221). Combining may be understood to involve taking individual objectsor indicators and integrating them into a form having at least oneunitary element. Examples may include taking multiple CSS files andcreating one CSS file having the information of the original multipleCSS files, taking multiple script files and creating one script filehaving the information of the original multiple script files, takingmultiple image files and creating one image file having the informationof the original multiple image files, taking multiple pointers andcreating one pointer having the information of the original multiplepointers, and the like. Accordingly, embodiments may include anelectronic data object combiner (203) to which a first electronicstorage medium (201) having multiple electronic data objects (202)stored thereon is responsive and electronic data indicator combiner(204) to which said second electronic storage medium (221) havingmultiple electronic data indicators (222) stored thereon is responsive.

Moreover, creating one pointer from multiple pointers may involvecreating one output having a size of up to 500 bytes less than the sizeof the multiple pointers. Accordingly, embodiments may include an up to500 byte reduce output size combiner.

For example, in various embodiments combining may involve creating atleast one common characteristic from separate characteristics. Asdiscussed for example above, characteristics may include file type, suchas CSS, script, image, or pointer. Other examples of characteristics mayinclude location characteristic, name characteristic, and addresscharacteristic. Accordingly, combiner in various embodiments may be acommon characteristic combination processor, a location characteristiccombination processor, a name characteristic combination processor, andan address characteristic combination processor.

Any suitable method of combining may be utilized. Embodiments mayinclude sequentially combining, such as wherein individual objects orpointers may be combined in succession, contiguously combining, such aswherein individual objects or pointers may be combined in contact,hierarchically combining, such as wherein individual objects or pointersmay be combined in rank, or the like. Accordingly, a combiner in variousembodiments may be a sequential combiner, a contiguous combiner, or ahierarchical combiner.

Of course, such acts of combining may act to reduce the size of thesekinds of files. In various embodiments, combining may involve creatingone CSS file from multiple CSS files including creating one CSS filehaving a size of up to 35.5% less than the size of said multiple CSSfiles, creating one script file from multiple script files includingcreating one script file having a size of up to 16.9% less than the sizeof said multiple script files, creating one image file from multipleimage files including creating one image file having a size of up to34.8% less than the size of said multiple image files, and creating onepointer from multiple pointers.

Accordingly, a combiner in various embodiments maybe a CSS filecombiner, including perhaps an up to 35.5% reduced CSS file sizecombiner; a script file combiner, including perhaps an up to 16.9%reduced script file size combiner, an image file combiner, includingperhaps an up to 34.8% reduce image file size combiner, and a pointercombiner.

Embodiments may involve associating a single combined electronic dataobject (202) at a first location (201) to a single combined dataindicator (222) at a second location (221), perhaps using principles forassociation as described elsewhere herein. Accordingly, embodiments mayinvolve an electronic data associator (205) responsive to an electronicobject combiner (203) and an electronic data indicator combiner (204).

Embodiments may involve effectively compressing at least one requestfrom a second location (221) for at least one electronic data object(102) at a first location (101) with said single combined electronicdata indicator at the second location (221) and effectively compressingprovision from the first location (101) of the electronic data object(102) to said second location (221) with the single combined electronicdata object at said first location (101). Accordingly, embodiments mayinclude an electronic data object request and provide effectivecompressor (206) responsive to an electronic data associator (205) andto which a first electronic storage medium (201) and a second electronicstorage medium (221) are responsive.

This may involve, for example, effectively compressing a request from aclient to a server for information on the server necessary to load a Webpage at the client, including information such as CSS files, scriptfiles, or image data, wherein the client may utilize a combined pointerpointing to a combined CSS file, combined script file, or combined imagedata file. Effective compression may be achieved, for example, by usinga single combined pointer in place of multiple separate pointers torequest information, and using a single combined CSS, script, or imagefile to provide information, rather than using multiple separate CSS,script, or image files.

Effectively compressing may be understood to include achievingcompression effects in the handling of electronic data, and may beunderstood to include doing so without compressing or perhaps withoutsolely compressing. For example, if compression technologies may achievetime, speed, or similar efficiencies in the storage and transmission ofelectronic data by reducing the size of electronic data; effectivecompression may involve achieving the same or comparable efficiencies bycombining electronic data. Stated differently, in at least someembodiments, effectively compressing may involve the capability ofproducing a compression result without using compression.

Examples of effective compression may be found in FIGS. 16-19.

Accordingly embodiments may include a non-compression system (207) and acompression effect system (208).

In some embodiments, achieving compression effects may involveleveraging a combination efficiency. Accordingly, embodiments mayinclude a combination efficiency leverage system (209).

One example of a combination efficiency leverage system may be stated asfollows:

-   -   On average, one electronic data object representing the        consolidated input of multiple electronic data objects may        compress to a number of bytes that may be, on average, less than        the number of bytes of compressing each of the multiple        electronic data objects individually. This may be due to the        fact that compression works best on larger files containing        repeated information.    -   In a first example, input may contain one or more HTML elements        with the name “link,” each referring to a different location of        electronic data objects:        -   <link href=“style1.css” rel=“stylesheet”type=“text/css” />        -   <link href=“style2.css” rel=“stylesheet”type=“text/css” />    -   If style1.css contains the following information:        -   #outer {        -   background-color: #ffffff;        -   }    -   . . . and is compressed, there may not be much opportunity for        compression. If style2.css contains the following information:        -   #inner {        -   background-color: #ffffff;        -   }    -   . . . and is compressed, there is not much opportunity for        compression. However, when:        -   <link href=“style1.css” rel=“stylesheet”type=“text/css” />        -   <link href=“style2.css” rel=“stylesheet”type=“text/css” />    -   . . . is replaced with:        -   <link href=“./CS.sc?{%}” rel=“stylesheet”type=“text/css” />    -   . . . and ./CS.sc?{%} contains the following information:        -   #outer {            -   background-color: #ffffff;        -   }        -   #inner {            -   background-color: #ffffff;        -   }    -   . . . and is compressed, there may be a greater opportunity for        compression.    -   For a second example, an input may contain one or more HTML        elements with the name “script,” each referring to a different        location of said electronic data objects:        -   <script type=“text/javascript” src=“script1.js”></script>        -   <script type=“text/javascript” src=“script2.js”></script>    -   If script1.js contains the following information:        -   function foo( ){            -   var x=1;        -   }    -   . . . and is compressed, there may not much opportunity for        compression. If script2.js contains the following information:        -   function bar( ){            -   var y=2;        -   }    -   . . . and is compressed, there may not much opportunity for        compression. However, when:        -   <script type=“text/javascript” src=“script1.js”></script>        -   <script type=“text/javascript” src=“script2js”></script>    -   . . . Is replaced with:        -   <style type=”text/javascript” src=“./JS.sc?{%}”></script>    -   . . . and ./JS.sc?{%} contains the following information:        -   function foo( ){            -   var x=1;        -   }        -   function bar( ){            -   var y=2;        -   }    -   . . . and is compressed, there may be a greater opportunity for        compression.    -   For a third example, an input may contain one or more HTML        elements with the name “img,” each referring to a different        location of said electronic data objects:        -   <img src=“image1.gif” />        -   <img src=”image2.gif” />    -   If image1.gif contains the following information:        -   71, 73, 70, 56, 57, 97, 1, 0, 1, 0, 128, 0, 0, 255, 255,            255, 255, 255, 255, 33, 249, 4, 1, 10, 0, 1, 0, 44, 0, 0, 0,            0, 1, 0, 1, 0, 0, 2, 2, 76, 1, 0, 59    -   . . . and is compressed, there may not much opportunity for        compression. If image2.gif contains the following information:        -   71, 73, 70, 56, 55, 97, 1, 0, 1, 0, 128, 1, 0, 0, 0, 0, 255,            255, 255, 44, 0, 0, 0, 0, 1, 0, 1, 0, 0, 2, 2, 68, 1, 0, 59    -   . . . and is compressed, there may not much opportunity for        compression. However, when:        -   <img src=“image1.gif” />        -   <img src=”image2.gif” />    -   . . . is replaced with:        -   <img src=“./IS.sc?{%1}” style=“background:url(./IS.sc?{%2})            %3px %4px no-repeat;” />        -   <img src=“./IS.sc ?{%1}”            style=“background:url(./IS.sc?{%2})%3px %4px no-repeat;” />    -   . . . and ./IS.sc?{%} contains the following information:        -   1, 73, 70, 56, 57, 97, 1, 0, 1, 0, 128, 0, 0, 255, 255, 255,            255, 255, 255, 33, 249, 4, 1, 10, 0, 1, 0, 44, 0, 0, 0, 0,            1, 0, 1, 0, 0, 2, 2, 76, 1, 0, 59, 71, 73, 70, 56, 55, 97,            1, 0, 1, 0, 128, 1, 0, 0, 0, 0, 255, 255, 255, 44, 0, 0, 0,            0, 1, 0, 1, 0, 0, 2, 2, 68, 1, 0, 59    -   . . . and is compressed, there may a greater opportunity for        compression.

More generally, in various embodiments, leveraging may involve replacingmultiple programming code instructions having different sourceattributes with a single programming code instruction having a singlesource attribute. A single source attribute may be a single combinedelectronic data object (102) and a single combined electronic dataindicator (222). The programming code may be HTML, and the programmingcode instruction may include <link href= . . . >, <script type= . . . >,<img src= . . . >, and <style type= . . . >. Of course, the foregoingexample is merely illustrative, and should not be construed to limit thebroader principles underlying the same, particularly as relates toleveraging combination efficiencies, though not limited to the same.Accordingly, embodiments may involve a multiple programming codeinstruction replacement processor (210) and a single programming codeinstruction single source attribute processor (211).

In various embodiments, effectively compressing may involve avoidingmultiple requests and avoiding multiple provisions of electronic dataobjects (202). For example, wherein objects and pointers may becombined, as described herein, such combinations may avoid the necessityof requesting and providing objects stored at disparate locations.Accordingly, embodiments may include a multiple request avoidanceprocessor and a multiple provision avoidance processor (212).

In various embodiments, effectively compressing may involve using a dataassociation in an HTTP header to request and provide electronic data.Effectively compressing also may involve a client-server transaction, aTCP/IP transaction, an FTP transaction, an HTTP transaction, a WorldWide Web transaction, a networked environment transaction, or the like.Accordingly, a compressor in various embodiments may be a client-servertransaction effective compressor, a TCP/IP transaction effectivecompressor, a FTP transaction effective compressor, a HTTP transactioneffective compressor, a World Wide Web transaction effective compressor,and a networked environment effective compressor.

In various embodiments, effectively compressing may involve using a dataassociation to request and provide an electronic data object (202)individually. For example, such use may involve separately providing anelectronic data object (202) using one electronic data indicator (222)of the data association, even wherein the data association may includeother associated objects and indicators. Similarly, such use may involveproviding multiple electronic data objects (202) using multipleelectronic data indicators (222) of the data association. Moreover, suchprovision may via one electronic data exchange transaction, in as muchas the use of a single data association may obviate the need to accessmultiple disparate locations of such objects. It may be seen thatembodiment may involve providing multiple electronic data objects (102)using multiple electronic data indicators (222) and avoiding multipleelectronic data exchange transactions. Naturally, embodiments also mayinvolve transmitting electronic data from the first location (201) tothe second location (221).

Accordingly, embodiments may include an individual electronic dataobject request and provision system having an associated data processor(214), an electronic data object separate provision processor (215), anelectronic data indicator use processor (216), a multiple electronicdata object provision processor (217), and a multiple electronic dataindicator use processor (218). Moreover, embodiments may comprise asingle electronic data exchange transaction system (219) and a multipleelectronic data exchange transaction avoidance system (220).

Now with reference primarily to FIG. 3, embodiments of the inventivetechnology may involve a method for increasing the effective rate oftransmitting electronic data and an electronic data transmissioneffective rate augmentation apparatus.

The method may involve storing an electronic data object (302) at afirst location, such as perhaps a first electronic storage medium (301),perhaps as described elsewhere herein.

Embodiments may involve linking said first location (301) to a secondlocation, such as perhaps a second electronic storage medium (309), viaan electronic data communications network (303), perhaps as describedelsewhere herein.

Embodiments may involve accessing the electronic data communicationsnetwork (303) utilizing an electronic message assembly protocol and anelectronic message addressing protocol. The term accessing may beunderstood to include making the network available to one or moreelectronic storage media to send and receive electronic data from thestorage media. Moreover, in various embodiments, the electronic messageassembly protocol may be TCP and the electronic message addressingprotocol may be IP. Accordingly, embodiments may include an access point(304) responsive to an electronic message assembly protocol (305) and anelectronic message addressing protocol (306).

Additionally, the electronic data communications network (303) invarious embodiments may be a network having a benchmark networktransmission rate for electronic data transmission via the networkutilizing the electronic message assembly protocol and the electronicmessage addressing protocol. Such a benchmark may be any suitablestandard or reference by which an accepted value for the rate oftransmission of given types of electronic data may be quantified.Moreover, the benchmark may be understood to be tied to the conventionalinfrastructure elements of the network, including for example thestandard electronic message assembly protocol and electronic messageaddressing protocol utilized by the network. Accordingly, embodimentsmay involve a benchmark network transmission rate (307) of an electronicdata communications network (303) responsive to an electronic messageassembly protocol (305) and an electronic message addressing protocol(306).

Embodiments may involve transmitting an electronic data object (302)from the first location (301) to the second location (309) via theelectronic data communications network (303) at an effectivetransmission rate greater than the benchmark network transmission rate.

Accordingly, embodiments may involve an electronic data objecttransmission effective rate augmenter (308) responsive to a benchmarknetwork transmission rate (307) and to which a first electronic storagemedium (301), a second electronic storage medium (309), and anelectronic data communications network (303) are responsive

An effective transmission rate should be understood to include achievinga rate improved over the benchmark transmission rate, perhaps withoutactually transmitting data faster than the network's benchmarktransmission rate permits. For example, if the electronic communicationsnetwork transmits given types of electronic data at its benchmark rate,achieving an effective transmission rate greater than the benchmark mayinvolve, for example, changing the nature of the input data, shorteningthe total length of the communication path, and the like, each perhapswhile still transmitting electronic data at the network's benchmarktransmission rate. Stated differently, in at least some embodiments,transmitting at an effective network transmission rate may involve thecapability of producing an end result of transmitting electronic data ata greater rate, without actually achieving such greater rate.

Accordingly, transmitting may involve achieving an effective networktransmission rate greater than a benchmark network transmission bytransmitting up to 52.3% less data, and embodiments may include an up to52.3% less data transmission effective rate augmenter.

Examples of transmitting an effective network transmission rate greaterthan the benchmark network transmission rate may be found in FIGS.16-19.

Now with reference primarily to FIG. 4, embodiments of the inventivetechnology may involve a method for combining electronic spatial dataand an electronic spatial data combination apparatus.

Embodiments may include multiple electronic spatial data objects (402)at a first location, such a first electronic storage medium (401),perhaps as described elsewhere herein.

Embodiments may involve automatically accessing multiple electronicspatial data objects (402). The term accessing may be understood toinclude making such electronic spatial data objects (402) available forelectronic manipulation, such as for example by the commands of aprogramming language, by action of electronic processing, or the like.In some embodiments, accessing may involve storing at least oneelectronic spatial data object (402) at a first location (401) andstoring at least one electronic spatial data indicator (425) at a secondlocation (424) associated to the electronic spatial data object (402) atthe first location.

Embodiments further may involve transmitting electronic data from thefirst location (401) to the second location (424). Accordingly,embodiments may include an automated electronic spatial data objectaccessor (403) responsive to multiple electronic data objects (402).

Electronic spatial data objects (402) may be understood to have spatialcharacteristics when their information content derives both from thevalue at a location plus the relationship of such location to anotherlocation, for example in a multi-coordinate system, such as an x, ysystem. Examples of electronic spatial data objects (402) may includeimage files, such as JPG files, GIF files, or PNG files.

Embodiments may involve automatically identifying at least onecharacteristic of each electronic spatial data object (402) relevant tocontiguous combination of multiple electronic spatial data objects(402). This may involve seeking and recognizing a characteristic in eachobject to be used in a combination technique based on suchcharacteristic. Examples of such characteristics may include identifyingboundary, area, size, file format, image width, and image heightcharacteristics of an electronic spatial data object (402), includingboth as related to the properties of the electronic data itself and asto any representation of such spatial data, for example an image.Accordingly, embodiments may include an automated contiguous combinationcharacteristic identifier (404) responsive to an automated electronicspatial data object accessor (403). Such an identifier in variousembodiments may be a boundary identifier, an area identifier, a sizeidentifier, a file format identifier, an image width identifier, or animage height identifier.

For example, an electronic spatial data object (402) may contain inputinformation having an HTML element with the name “img” that looks likethe following:

-   -   <img src=“image1.jpg” />

If the value for the “src” attribute refers to a resource that can beread, an attempt can be made to load the data read from the value of thesrc attribute into a bitmap object, the implementation of which may bespecific to the platform on which the method is executing (Windows,Linux, etc.) If the attempt to load the bitmap succeeds, the imageformat, width, and height may be identified. Otherwise, the inputinformation may be skipped. If the image format, width, and height aresupported, the input may be processed. Otherwise, the input informationmay be skipped.

More generally, in various embodiments, identifying may involveexecuting at least one programming code instruction having a sourceattribute, loading the data of the source attribute into an electronicspatial data object map, and identifying a characteristic utilizing theelectronic spatial data map. The programming code may be, for example,HTML, and the instruction may be, for example, <img src= . . . >,although other programming languages and instructions may be understoodto be applicable as well. Accordingly an identifier in variousembodiments may include a source attribute programming code instructionexecution processor (408), a source attribute data loading processor(409) responsive to a source attribute programming code instructionexecution processor (408), an electronic spatial data object map loadingprocessor (410) responsive to a source attribute data loading processor(409), and a characteristic identification processor (411) responsive toan electronic spatial data object map loading processor (410).

Embodiments may involve automatically aggregating multiple electronicspatial data objects (402) having an automatically identifiedcharacteristic. Aggregating may be understood to involve bringingtogether those objects having the identified characteristic and makingthem available for subsequent action based on the identifiedcharacteristic. Accordingly, embodiments may involve an automatedelectronic spatial data aggregator (405) responsive to an automatedcontiguous combination characteristic identifier (404).

Embodiments may involve automatically contiguously combining multipleelectronic spatial data objects (402) using each automaticallyidentified characteristic. Combining may be understood to involve takingindividual objects or indicators and integrating them into a form havingat least one unitary element. Examples may include joining the objectsautomatically identified boundaries, minimizing automatically identifiedareas of the object, minimizing automatically identified sizes of theobjects, combining the objects by file format, combining the objects byimage width, and combining the objects by image height. Moreover, theseexamples may be illustrative of contiguously combining multipleelectronic spatial data objects (402). Accordingly, embodiments mayinvolve an automated electronic spatial data object contiguous combiner(406) responsive to an automated electronic spatial data aggregator(405), which in various embodiments may include an automaticallyidentified boundary processor (412), an automatically identified areaminimization processor (413), an automatically identified sizeminimization processor (414), an automatically identified file formatcombination processor (415), and an automatically identified image widthcombination processor (416), and an automatically identified imageheight combination processor (417).

In one embodiment, an example of contiguously combining multipleelectronic spatial data objects may be as follows:

-   -   1. Let the variable y equal 0.    -   2. Sort the collection of objects so that an object A with a        width greater than object B is located higher in the list than        object B.    -   3. In the case when two object have the same width, sort the        collection of object so that an object A with a height greater        than object B is located higher in the list than object B.    -   4. In the case when two object have the same width and the same        height, it does not matter if object A is located higher in the        list than object B or if object B is located higher in the list        than object A.    -   5. Go through the collection of object, starting with the object        located highest in the list and working toward the object        located lowest in the list.    -   6. If the object has already been added to a combined object,        skip it.    -   7. If the combined object has not been created, create it with a        width of the object and a height of the object. Otherwise, if        the combined object has been created, let the variable y equal        the height of the combined object, create a new combined object        with a width of the combined object and a height equal to the        height of the combined object plus the height of the object.        Copy the combined object to the new combined object. Set the        combined object equal to the new combined object.    -   8. Add the object to the combined object at X coordinate 0 and Y        coordinate equal to the y variable.    -   9. Create a collection to hold one or more rectangles, each        rectangle comprising of an X coordinate, a Y coordinate, a        width, and a height.    -   10. Create a rectangle with an X coordinate equal to the width        of the object, a Y coordinate equal to the y variable, a width        equal to the width of the combined object minus the width of the        object, and a height equal to the height of the object.        Effectively, this is the available space to the right of the        object, extending to the right edge of the combined object and        to the bottom edge of the combined object. Add the rectangle to        the collection of rectangles.    -   11. Go through the collection of objects, starting with the next        object, working toward the object located lowest in the list.    -   12. If the next object has already been added to the combined        object, skip it.    -   13. Go through the collection of rectangles.    -   14. Do the following if the rectangle's width is greater than or        equal to the next object's width and the rectangle's height is        greater than or equal to the next object's height: Add the next        object to the combined object at an X coordinate equal to the        rectangle's X coordinate and a Y coordinate equal to the        rectangle's Y coordinate. Create a 2nd rectangle with an X        coordinate equal to the rectangle's X coordinate plus the width        of the next object, a Y coordinate equal to the rectangle's Y        coordinate, a width equal to the width of the combined object        minus the rectangle's X coordinate minus the next object's        width, and a height equal to the next object's height.        Effectively, this 2nd rectangle is the available space to the        right of the next object, extending to the right edge of the        combined object and the bottom edge of the next object. Add the        2nd rectangle to the collection of rectangles. Create a 3rd        rectangle with an X coordinate equal to rectangle's X        coordinate, a Y coordinate equal to the rectangle's Y coordinate        plus the height of the next object, a width equal to the width        of the combined object minus the rectangle's X coordinate, and a        height equal to the rectangle's height minus the next object's        height. Effectively, this 3rd rectangle is the available space        to the bottom of the next object, extending to the right edge of        the combined object and the bottom of the rectangle. Add the 3rd        rectangle to the collection of rectangles. Remove the rectangle        from the collection of rectangles.

More generally, combining electronic spatial data objects (402) mayinvolve creating an order of the objects based on the identifiedcharacteristics, eliminating redundant objects from the order, andsequentially contiguously combining each object successively to create asingle contiguously combined electronic spatial data object based on theorder. Accordingly, embodiments may include a multiple electronicspatial data objects ordering processor (418) responsive to saidautomated contiguous combination characteristic identifier (404), aredundant electronic spatial data object eliminator (419) responsive tosaid multiple electronic spatial data objects ordering processor (418),and a successive order electronic spatial data object sequentialcontiguous combiner (420) responsive to said redundant electronicspatial data object eliminator (419).

Creating a single contiguously combined electronic spatial data objectin various embodiments may involve creating a single contiguouslycombined electronic spatial data object up to 34.8% less than the sizeof the multiple electronic spatial data objects (402), creating a singlecontiguously combined electronic spatial data object having at least onecommon characteristic derived from a characteristic identified from themultiple electronic spatial data objects (402), and, of course, creatingan image file, for example a JPG, GIF, or PNG file. Accordingly,embodiments may include an up to 34.8% reduced size electronic spatialdata object contiguous combiner, a multiple electronic spatial dataobject common characteristic identification processor (421), and animage file creator, naturally include a JPG creator, a GIF creator, anda PNG creator.

Embodiments also may include an electronic data transmitter (423), asecond electronic storage medium (424), and an electronic data indicator(425) stored on a second electronic storage medium (424).

Now with reference primarily to FIG. 5, embodiments of the inventivetechnology may involve a method for threshold combining electronic dataand an electronic data threshold combination apparatus.

Embodiments may involve automatically accessing multiple electronic dataobjects (502). The term accessing may be understood to include makingsuch electronic data objects (502) available for electronicmanipulation, such as for example by the commands of a programminglanguage, by action of electronic processing, or the like. Theelectronic data objects (502) in various embodiments may includemultiple CSS data objects, multiple script data objects, and multipleimage data objects. Accordingly, embodiments may include multipleelectronic data objects (502) stored at a first location, such as afirst electronic storage medium (501) and an automated electronic dataobject accessor (503) responsive to said multiple electronic dataobjects (502). In various embodiments, such objects may include multipleCSS data objects, multiple script data objects, and multiple image dataobjects.

Embodiments further may involve storing at least one electronicindicator (538) at a second location, such as a second electronicstorage medium (537), associated to an electronic data object (502), andtransmitting the electronic data from a first location, such as firstelectronic storage medium (501), to the second location, such as secondelectronic storage medium (537). Accordingly, embodiments may include anelectronic data transmitter linking a first electronic storage medium(501) and a second electronic storage medium (537).

Embodiments may involve automatically identifying at least onecharacteristic of each electronic data object (502) relevant to athreshold criterion for combining the objects. This may involve seekingand recognizing a characteristic in each object to be used in evaluatinga threshold for determining whether or not the object will be combinedwith other objects.

Examples of such characteristics may include object size and objectnumber. Accordingly, embodiments may include an automated thresholdcriterion combination characteristic identifier (504) responsive to anautomated electronic data object accessor (503), which in embodimentsmay be an object size identifier, object number identifier, or the like.

In one example, automatically identifying may involve the following:

-   -   If the object contains an HTML element with the name “link” or        “script” or “img” it is automatically identified as All.    -   If the object contains an HTML element with the name “link” or        “script” or “img” and there is no query string in the addressed        electronic data indicator it is automatically identified as No        Query String.    -   For example, the following addressed electronic indicator has a        query string:        -   <img src=“image.jpg?XYZ=123” />    -   And for example, the following addressed electronic indicator        does not have a query string:        -   <img src=“image jpg” />    -   If the object contains an HTML element with the name “link” and        the addressed electronic indicator ends with “.css” it is        automatically identified as CSS, JS, Image.    -   If the object contains an HTML element with the name “script”        and the addressed electronic indicator ends with “.js” it is        automatically identified as CSS, JS, Image.    -   If the object contains an HTML element with the name “img” and        the addressed electronic indicator ends with a supported        extension (such as “.gif” for GIF images, “.jpg” for JPEG        images, or “.png” for PNG images) it is automatically identified        as CSS, JS, Image.

More generally, automatically identifying may involve automaticallyidentifying an all characteristic, which may involve automaticallyidentifying as all, HTML programming code having at least one elementwith a name selected from the group consisting of link, script, img, orstyle. Accordingly, various embodiments may include an allcharacteristic identifier, which may include an HTML programming codelink name element processor (508), an HTML programming code script nameelement processor (509), and an HTML programming code img name elementprocessor (510).

More generally, automatically identifying may involve automaticallyidentifying a no query string characteristic, which may involveautomatically identifying as no query string, HTML programming codehaving at least one element with a name selected from the groupconsisting of link, script, img, and having no query string in anassociated electronic data indicator. Accordingly, various embodimentsmay include a no query string characteristic identifier, which mayinclude HTML programming code link name element processor (515), an HTMLprogramming code script name element processor (516), and an HTMLprogramming code img name element processor (517), and wherein each saidprocessor further comprises a processor responsive to an associatedelectronic indicator having no query string (518).

More generally, automatically identifying may involve automaticallyidentifying a CSS characteristic, which may involve automaticallyidentifying as CSS, HTML programming code having at least one elementwith the name link, and having an associated electronic data indicatorcontaining a .css element. Accordingly, various embodiments may includea CSS characteristic identifier (512), which may include HTMLprogramming code link name element processor (519), wherein saidprocessor further comprises a processor responsive to an associatedelectronic indicator containing a .css element or css file extension(520).

More generally, automatically identifying may involve automaticallyidentifying a script characteristic, which may involve automaticallyidentifying as script, HTML programming code having at least one elementwith the name script, and having an associated electronic data indicatorcontaining an element selected from the group consisting of a .jselement and a script file extension. Accordingly, various embodimentsmay include a script characteristic identifier (513), which may includeHTML programming code script name element processor (521), wherein saidprocessor further comprises a processor responsive to an associatedelectronic indicator containing an element selected from the groupconsisting of a .js element, script element and a script file extension(522).

More generally, automatically identifying may involve automaticallyidentifying an image characteristic, which may involve automaticallyidentifying as image, HTML programming code having at least one elementwith the name img, and having an associated electronic data indicatorcontaining an element selected from the group consisting of .jpg, .gif,.png, and an image file extension. Accordingly, various embodiments mayinclude a image characteristic identifier (514), which may include HTMLprogramming code img name element processor (523), wherein saidprocessor further comprises a processor responsive to an associatedelectronic indicator containing an element selected from the groupconsisting of .jpg, .gif, .png, img element and image file extension(524).

Embodiments may involve automatically aggregating multiple electronicdata objects (502) having at least one automatically identifiedcharacteristic relevant to a threshold criterion for combining theobjects. Aggregating may be understood to involve bringing togetherthose objects having the identified characteristic and making themavailable for subsequent action based on the identified characteristic.Accordingly, embodiments may include an automated electronic data objectaggregator (505) responsive to an automated threshold criterioncombination characteristic identifier (504).

Embodiments may involve automatically determining if a thresholdcriterion for combining multiple electronic data objects (502) has beensatisfied. Accordingly, embodiments may include an automated thresholdcriterion determiner (506) responsive to an automated electronic dataobject aggregator (505).

In one example, automatically determining may involve storing acollection of character sequences generated that uniquely identify oneor more electronic data objects (502). When the collection contains morecharacter sequences than a threshold for such character sequences, itmay be automatically determined that the threshold has been exceeded.Accordingly, embodiments may include a unique character sequenceidentification generator (528) responsive to said multiple electronicdata objects (502), a unique character sequence identification numberdetermination processor (529) responsive to said unique charactersequence identification generator (528), and a unique character sequenceidentification threshold criterion processor (530) responsive to saidunique character sequence identification number determination processor(529).

Naturally, any suitable criterion capable of automated electronicevaluation may be utilized as a threshold criterion.

More generally, automatically determining may involve automaticallydetermining a threshold value for said multiple electronic data objects(502) based on an automatically identified characteristic for each saidelectronic data object (502) individually, automatically comparing theautomatically determined threshold value to a threshold criterion, andautomatically evaluating if the threshold criterion has been exceededbased on an automatic comparison. Accordingly, embodiments may includean automated multiple electronic data object threshold valuedetermination processor (525) responsive to an automated individualelectronic data object identified characteristic processor, which mayinclude an automated threshold criterion comparator (526) and anautomated threshold criterion evaluator (527).

Embodiments may involve automatically combining multiple electronic dataobjects (502) in accordance with an automatic determination if athreshold criterion for combining the objects has been satisfied.Combining may be understood to involve taking individual objects andintegrating them into a form having at least one unitary element.Accordance may be evaluated based on the specific threshold criterioninvolved—some embodiments, for example, may involve automaticallycombining objects if a threshold criterion has been met or exceeded andautomatically not combining objects if a threshold criterion has notbeen met or exceeded. Accordingly, embodiments may include an automatedelectronic data object combiner (507) responsive to an automatedthreshold criterion determiner (506), which may include an exceededthreshold value combiner.

Various embodiments may involve automatically effecting a fallbackcombination if a threshold criterion has been met or exceeded. Oneexample of a fallback combination may be stated as follows:

-   -   Per input, per type (styles, scripts, images):    -   Start at the All state.    -   If in the All state and the number of character sequences that        uniquely identify a consolidated input exceeds the threshold,        automatically effect a fallback to the No    -   Query String state. Clear the collection of character sequences        generated that uniquely identify a consolidated input.    -   If in the No Query String state and the number of character        sequences that uniquely identify a consolidated input exceed the        threshold, automatically effect a fallback to the CSS, JS, Image        state. Clear the collection of character sequences generated        that uniquely identify a consolidated input.    -   If in the CSS, JS, Image state and the number of character        sequences that uniquely identify a consolidated input exceeds        the threshold, automatically effect a fall back to the None        state. Clear the collection of character sequences generated        that uniquely identify a consolidated input.

More generally, embodiments may involve falling back hierarchically bystate. This may involve first falling back to a no query string statefrom an all state, if a number of character sequences uniquelyidentifying said multiple electronic data objects exceeds a thresholdcriterion number for said number of character sequences; second fallingback to a state selected from the group consisting of a CSS state, a JSstate, and an image state, from said no query string state, if a numberof character sequences uniquely identifying said multiple electronicdata objects exceeds a threshold criterion number for said number ofcharacter sequences, and wherein said multiple electronic data objectsare selected from the group consisting of CSS data, JS data, and imagedata; and third falling back to a none state from said state selectedfrom said group consisting of a CSS state, a JS state, and an imagestate, if a number of character sequences uniquely identifying saidmultiple electronic data objects exceeds a threshold criterion numberfor said number of character sequences, and wherein said multipleelectronic data objects are selected from said group consisting of CSSdata, JS data, and image data.

Accordingly, in various embodiments an automated electronic data objectcombiner (507) may be a fallback combination combiner utilizing afallback combination hierarchy (531) having a no query string state(532), a CSS, JS, image state (533), and a none state (534), perhaps asdescribed above.

Moreover, an automated electronic data object combiner (507) in variousembodiments may be all state conditional all multiple electronic dataobject combiner; a no query string state conditional multiple electronicdata object combiner, wherein said combiner is responsive only tomultiple electronic data objects having no query string in an associatedelectronic indicator; a CSS state conditional multiple electronic dataobject combiner, wherein said combiner is responsive only to saidmultiple electronic data objects comprising CSS data and having anassociated electronic data indicator containing a .css element; a JSstate conditional multiple electronic data object combiner, wherein saidcombiner is responsive only to said multiple electronic data objectscomprising script data and having an associated electronic dataindicator containing a .js element; an image state conditional multipleelectronic data object combiner, wherein said combiner is responsiveonly to said multiple electronic data objects comprising image data andhaving an associated electronic data indicator containing an elementselected from the group consisting of JPG data, GIF data, PNG data; anda none state conditional multiple electronic data object non-combiner.

Moreover, automatically combining electronic data objects (502) mayinvolve combining the objects according to identified state. One exampleof this may be stated as follows:

-   -   Per input, per type (styles, scripts, images):    -   If in the All state, consolidate all input.    -   If in the No Query String state, only consolidate input that        does not have a query string in an addressed electronic data        indicator.    -   If in the CSS, JS, Image state, and the input is a link, only        consolidate input that has an addressed electronic data        indicator ending with “.css”    -   If in the CSS, JS, Image state, and the input is a script, only        consolidate input that has an addressed electronic data        indicator ending with “.js”    -   If in the CSS, JS, Image state, and the input is an image, only        consolidate input that has an addressed electronic data        indicator ending with a supported extension (such as “.gif” for        GIF images, “.jpg” for JPEG images, or “.png” for PNG images).    -   If in the None state, consolidate no input.

More generally, automatically combining according to state may involvecombining all multiple electronic data objects, if in an all state;combining only multiple electronic data objects having no query stringin an associated electronic indicator, if in a no query string state;combining only multiple electronic data objects having an associatedelectronic data indicator containing a .css element, if in a CSS state,wherein said multiple electronic data objects comprise CSS data;combining only multiple electronic data objects having an associatedelectronic data indicator containing a .js element, if in a JS state,wherein said multiple electronic data objects comprise script data; andcombining only said multiple electronic data objects having anassociated electronic data indicator containing an element selected fromthe group consisting of JPG data, GIF data, PNG data, or image fileextension data, if in an image state, wherein said multiple electronicdata objects comprise image data.

The method for threshold combining electronic data in variousembodiments may be a method for safeguarding the operation of acomputing device, perhaps generally by avoiding detrimental operatingconditions when the computing device is supplied with too much data forsafe processing. As an example, the architecture or the World Wide Weboften may resulting in the dynamic generation of electronic data, toomuch of which can adversely impact the operation of server or clientcomputing devices. The threshold aspects described herein may allow forcompensating for dynamic generation of electronic data, includingcompensating for CSS information, script information, image information,World Wide Web page content information, and like kinds of information.Accordingly, embodiments may include a computing device operationsafeguard (535) and dynamically generated electronic data compensator(536), which may be a CSS information compensator, a script informationcompensator, an image information compensator, and a World Wide Web pagecontent information compensator.

Now with reference primarily to FIG. 6, embodiments of the inventivetechnology may involve a method for compressing electronic spatial dataand an electronic spatial data compression apparatus.

Embodiments may involve accessing multiple electronic spatial dataobjects (602). Accordingly, embodiments may include an electronicspatial data object accessor (603) responsive to multiple electronicspatial data objects (602). The term accessing may be understood toinclude making such electronic spatial data objects (602) available forelectronic manipulation, such as for example by the commands of aprogramming language, by action of electronic processing, or the like.In some embodiments, accessing may involve storing at least oneelectronic spatial data object (602) at a first location, such as afirst electronic storage medium (601), and storing at least oneelectronic spatial data indicator (617) at a second location, such as asecond electronic storage medium (618), associated to the electronicspatial data object (602) at the first location. Embodiments further mayinvolve transmitting electronic data from the first location (601) tothe second location (618).

Accordingly, embodiments may include multiple electronic spatial dataobjects (602) stored on at least one electronic storage medium (601),multiple electronic data indicators (617) stored on a second electronicstorage medium (618), and an electronic transmitter (619) linking afirst electronic storage medium (601) and a second electronic storagemedium (618).

Electronic spatial data objects (602) may be understood to have spatialcharacteristics when their information content derives both from thevalue at a location plus the relationship of such location to anotherlocation, for example in a multi-coordinate system, such as an x, ysystem. Examples of electronic spatial data objects (402) may includeimage files, such as JPG files, GIF files, or PNG files.

Embodiments may involve aggregating multiple electronic spatial dataobjects (602) for combining the objects. Aggregating may be understoodto involve bringing together those objects having the identifiedcharacteristic and making them available for subsequent action based onthe identified characteristic. Accordingly, embodiments may involve anelectronic spatial data object aggregator (604) responsive to anelectronic spatial data object accessor (603).

Embodiments may involve combining multiple electronic spatial dataobjects (602). Combining may be understood to involve taking individualobjects and integrating them into a form having at least one unitaryelement. Examples may include sequentially combining, such as whereinindividual objects may be combined in succession, contiguouslycombining, such as wherein individual objects combined in contact,hierarchically combining, such as wherein individual objects or pointersmay be combined in rank, combining the objects by file format, combiningthe objects by image width, and combining the objects by image height.Examples further may include creating at least one common characteristicfrom separate characteristics, such as a location characteristic, a namecharacteristic, an address characteristic, a file format characteristic,an image width characteristic, an image height characteristic, and thelike.

Accordingly, embodiments may include an electronic spatial data objectcombiner (605) responsive to an electronic spatial object aggregator(604), which may be a sequential combiner, a contiguous combiner, ahierarchical combiner, a file format combiner, an image width combiner,an image height combiner, or a common characteristic combiner. Moreover,a common characteristic combiner in various embodiments may have alocation characteristic processor (608), a name characteristic processor(609), an address characteristic processor (610), a file formatprocessor (611), an image width processor (612), and an image heightprocessor (613).

Embodiments may involve creating a single combined electronic spatialdata object, including of course a single combined image file, such as asingle combined JPG, a single combined GIF, a single combined PNG, orthe like. Accordingly, embodiments may include a single combinedelectronic spatial data object creator (606) responsive to an electronicspatial data object combiner (605), which may be in various embodimentsa single combined image file creator, such as a JPG creator, a GIFcreator, and a PNG creator.

Embodiments may involve electronically compressing a single combinedelectronic spatial data object to create an electronically compressedcombined electronic spatial data object. Any suitable compressiontechnology may be utilized, including for example GZIP and DEFLATE.Moreover, such compression may involve achieving improved compressionrelative to compressing multiple uncombined electronic spatial dataobjects (602), and may result in creating a compressed combinedelectronic spatial data object up to 34.8% less than the size of theuncombined multiple electronic spatial data objects (602). Accordingly,embodiments may include a combined electronic spatial data objectelectronic compressor (607) responsive to a single combined electronicspatial data object creator (606). Such a compressor in variousembodiments may include a GZIP compressor and a DEFLATE compressor, andmay utilize a relative improved compression achievement processor (614)and include an up to 34.8% relative improved compression achievementprocessor.

In this manner, electronically compressing a single combined electronicspatial data object may be seen as achieving multiple effectivecompression efficiencies, for example by leveraging a combinationefficiency and leveraging a compression efficiency to creating aneffective compression greater than that achievable simply by compressinguncombined electronic spatial data objects (602). Accordingly,embodiments may include a multiple effective compression efficiencyprocessor, which may include a combination efficiency processor and acompression efficiency processor.

Moreover, embodiments may involve retaining a separately usablefunctionality of each electronic spatial data object (602) individually,notwithstanding their compressed and combined nature in a resultingcompressed combined electronic spatial data object. For example,applications may involve separately utilizing at least one electronicspatial data object (602) individually, which may involve retrieving theobject individually, perhaps such as by retrieving an individual imagefile. Accordingly, embodiments may include an individual electronic dataobject separate use functionality preservation processor (615), whichmay include an individual electronic data object separate usefunctionality utilization processor. Embodiments also may include anindividual electronic spatial data object retrieval architecture (616),which may include an individual image file retrieval architecture.

Now with reference primarily to FIG. 7, embodiments of the inventivetechnology may involve a method for transmitting streamlined electronicdata and a streamlined electronic data transmission apparatus.

Embodiments may involve storing an electronic data object (702) at afirst location and an electronic data indicator (709) at a secondlocation, perhaps as described elsewhere herein. Accordingly,embodiments may include a first electronic storage medium (701) havingan electronic data object (702) stored thereon. Certain embodiment alsomay include a second electronic storage medium having a least oneelectronic data indicator stored thereon.

Embodiments further may involve automatically recognizing a use for theelectronic data object (702) at a second location (708), automaticallydetermining constituent parts of the electronic data object (702)necessary for use at the second location (708) and constituent parts ofthe electronic data object (702) unnecessary for use at the secondlocation (708), and automatically selectively removing the constituentparts of the electronic data object (702) unnecessary for use at thesecond location.

Accordingly, embodiments may include an automated second locationelectronic data object use recognizer (703) responsive to an electronicdata object (702), an automated electronic data object second locationuse constituent part determiner (704) responsive to said automatedsecond location electronic data object use recognizer (703), anautomated electronic data object second location dispensable constituentpart determiner (705) responsive to said automated second locationelectronic data object use recognizer (703), and an automatedstreamlined electronic data object creator (706) responsive to anautomated electronic data object second location use constituent partdeterminer (704) and an automated electronic data object second locationdispensable constituent part determiner (705).

The foregoing steps of recognizing, determining, and removing mayinvolve utilizing contextual awareness of the second location.Accordingly, embodiments may include a second location contextualawareness processors (708), (711), and (713).

With respect to the step of recognizing, for example, utilizingcontextual awareness may involve differentiating between capable usesand actual uses for an electronic data object (702) at the secondlocation. Such uses may be tied to the type of data comprising theelectronic data object (702), for example distinguishing among capableand actual uses for various styles in CSS data, distinguishing amongcapable and actual uses for scripts among script data, distinguishingamong capable and actual uses of images in image data, and the like.Accordingly, embodiments may involve a capable use differentiator (709)and an actual use differentiator (710), which differentiators naturallymay be CSS data differentiators, script data differentiators, and imagedata differentiators.

With respect to the steps of determining, utilizing a contextualawareness may involve determining constituent parts of the electronicdata object (708) to be actually used at the second location. Again,this may be tied to the type of data, for example, determining whichstyles of CSS data actually will be used, which scripts of script dataactually will be used, which images of image data actually will be used,and the like. Accordingly, embodiments may include an electronic dataobject constituent part second location actual use determiner (712).

With respect to the step of removing, utilizing contextual awareness mayinvolve selectively removing constituent parts of the electronic dataobject (702) that will not be used at the second location. This mayinvolve removing styles from CSS data that will not be used, scriptsfrom script data that will not be used, images from image data that willnot be used, and the like. Accordingly, embodiments may include a secondlocation dispensable constituent part selective remover (714).

In this manner, a streamlined electronic data object may be created atthe first location based on use characteristics at the second location,such that the streamlined data object may only include those constituentparts actually to be used at the second location.

For example, an electronic data object (702) in various embodiments maybe CSS data, script data, or image data. Conventional World Wide Webarchitectures may require a client to request and a server to providesets of CSS, script, and image information, even where not all of theinformation may actually be used at the client. Where a server canrecognize, determine, and selectively remove unnecessary informationbased on the actual uses for such information at the second location,for example by utilizing contextual awareness as described above,streamlined electronic data objects may be created.

Such streamlined electronic data objects naturally may result inefficiency increases in the storage and transmission for such objects.For example, embodiments may involve electronically transmitting astreamlined electronic data object from a first location (701) to asecond location (708), perhaps involving transmitting up to 52.3% lessdata as compared to unstreamlined transmission. Accordingly, embodimentsmay include an automated streamlined electronic data object transmitter(707) responsive to an automated streamlined electronic object creator,which may be in various embodiments a 52.3% less data automatedstreamlined electronic data object transmitter.

Now with reference primarily to FIG. 8, embodiments of the inventivetechnology may involve self-containing implementation of various methodsdescribed herein on one side of an electronic data exchange transaction.In some embodiments, this may involve avoiding counterpartimplementation of such a method on the other side of an electronic dataexchange transaction. An electronic data exchange transaction may beunderstood to include the transmission and processing of at least oneitem of electronic data, wherein such data may include electronic dataobjects and electronic data indicators. Examples of electronic dataexchange transactions may include server-client transactions, such asmay be used to load a Web page.

Self-containing implementation on one side of an electronic dataexchange transaction may involve effecting the method entirely at or byan implementing participant to the transaction, for example perhapsentirely at or by a server in a server-client transaction. Perhapssimilarly, avoiding counterpart implementation on another side of anelectronic data exchange transaction may involve taking no sua spontesteps to implement the method at or by a second or subsequentparticipant to the transaction, or perhaps relying on the implementingparticipant to initiate or carry out the steps of the method, forexample by a client in a server-client transaction. More generally,examples may include executing programming code on one side of anelectronic data exchange transaction and avoiding counterpart executionof programming code on another side of the transaction.

Accordingly, embodiments may include a one-sided self-contained dataexchange transaction implementation architecture (801) and an electronicdata exchange transaction opposed side counterpart implementationavoidance processor (802). Embodiments also may include a one-sidedelectronic data exchange transaction programming code executionprocessor (803) and an electronic data exchange transaction opposed sidecounterpart programming code execution avoidance processor (804).

In some embodiments, the execution of programming code may involveintermediating between a server and client. Intermediating may beunderstood to include acting between participants to the transaction.Even where the intermediary may be located at one of the participants tothe transaction, such as at a server, the intermediary may not interferewith the operation of the participant itself, such as where programmingcode may be executed independently from and perhaps not otherwiseinteract with the server's own software.

In a server-client architecture, for example, intermediating may involveallowing a request from a client to pass through the intermediary,allowing a server to process the request from the client withoutinterference from the intermediary, and intercepting a response from theserver to the client before allowing the response to pass through. Inthis example, the response may then be acted upon by the intermediary atthe point of intercept. Such a client request, for example, may be arequest for Web page information, and in some embodiments, interceptingmay involve accessing at least one combined electronic data objectutilizing at least one combined electronic data indicator, perhaps asdescribed elsewhere herein. Of course, this example relating to aserver-client architecture is for illustrative purposes only, and shouldnot be construed to limit the broader principles involved.

Accordingly, embodiments may involve an intermediary between a serverand a client (806), a client request pass-through (807), a server-sideclient request processor (808), a server response intercept (809), and acombined electronic data object access processor responsive to at leastone combined electronic data indicator (810).

In one example, self-containing implementation may be accomplished asfollows:

-   -   When a client sends a request for a Web page to a server, it may        be for static content or dynamic content. Either way, the        programming code may let the Web server handle the request, and        may intercept the response before it is sent to the client.    -   If the response does not have an HTTP status code of 200 (OK) or        does not have a Content-Type header with the value of        “text/html” it may cease processing.    -   It may retrieve values for the following headers from the        client:    -   Accept-Charset    -   Accept-Language    -   Cookie    -   User-Agent    -   It may retrieve values for the following headers from the        response:    -   Content-Encoding    -   Set-Cookie    -   If the response is already compressed, as indicated by a value        such as “gzip” or “deflate” in the Content-Encoding header, the        response may be decompressed.    -   It then may process the decompressed response.    -   If, during processing, it encounters an addressed data indicator        that is to be collocated or combined, it may request the        resource on behalf of the client by passing the following        headers:    -   Accept (Set to */*)    -   Accept-Encoding (Set to gzip, deflate)    -   Accept-Charset (Set to the value retrieved from the        Accept-Charset header from the client)    -   Accept-Language (Set to the value retrieved from the        Accept-Language header from the client)    -   Cookie (If the request is being made to the same host the        response was intercepted from, set to the value retrieved from        the Cookie header from the client + the value retrieved from the        Set-Cookie header from the response)    -   Host (Set to the host the request is being sent to)    -   Referer (Set to the URL of the response that was intercepted)    -   User-Agent (Set to the value retrieved from the User-Agent        header from the client)    -   X-Forwarded-For (Set to the IP address the response that was        intercepted is being sent to)    -   If the value retrieved from the Accept-Encoding header from the        client is “deflate” the new response may be compressed using        deflate without the gzip wrapper (this may save 22 bytes per        response).    -   If the value retrieved from the Accept-Encoding header from the        client is “gzip” the new response may be compressed using        deflate with the gzip wrapper.    -   After processing is complete, it may clear the original        response. It may send the new response to the client by passing        the following headers:    -   Content-Encoding (If the new response was compressed using        deflate without the gzip wrapper, set to “deflate”; if the new        response was compressed using deflate with the gzip wrapper, set        to “gzip”; otherwise, this header is not set)    -   Content-Type (Set to text/html)    -   Set-Cookie (Set to the value of the Set-Cookie header in the        original response, if applicable)    -   The programming code may expect one of the following subsequent        requests to come from the client for the consolidated inputs.        The addressed data indicators may refer to resources that the        Web server is not aware of. As such, rather than let the Web        server handle the request, the programming code may handle the        request.

If the request is for ./CS.se{go} where % is the character sequenceuniquely identifying the consolidated input, but no electronic dataobject exists for that character sequence, the programming code may letthe Web server handle the request, which may result in an HTTP statuscode of 404 (Not Found).

-   -   If the value retrieved from the Accept-Encoding header from the        client is “deflate” the electronic data object may be compressed        using deflate without the gzip wrapper (this saves 22 bytes per        response).    -   If the value retrieved from the Accept-Encoding header from the        client is “gzip” the electronic data object may be compressed        using deflate with the gzip wrapper.    -   It may send the electronic data object to the client by passing        the following headers:    -   Content-Type (Set to text/css)    -   Last-Modified (Set to now's date and time minus one day)    -   Expires (Set to now's date and time plus one year)    -   Cache-Control (Set to public, max-age=31536000)    -   Content-Encoding (If the new response was compressed using        deflate without the gzip wrapper, set to “deflate”; if the new        response was compressed using deflate with the gzip wrapper, set        to “gzip”; otherwise, this header is not set)    -   If the request is for ./JS.sc?{go} where % is the character        sequence uniquely identifying the consolidated input, but no        electronic data object exists for that character sequence, the        programming code may let the Web server handle the request,        which may result in an HTTP status code of 404 (Not Found).    -   If the value retrieved from the Accept-Encoding header from the        client is “deflate” the electronic data object may be compressed        using deflate without the gzip wrapper (this may save 22 bytes        per response).

If the value retrieved from the Accept-Encoding header from the clientis “gzip” the electronic data object may be compressed using deflatewith the gzip wrapper.

-   -   It may send the electronic data object to the client by passing        the following headers:    -   Content-Type (Set to text/javascript)    -   Last-Modified (Set to now's date and time minus one day)    -   Expires (Set to now's date and time plus one year)    -   Cache-Control (Set to public, max-age=31536000)    -   Content-Encoding (If the new response was compressed using        deflate without the gzip wrapper, set to “deflate”; if the new        response was compressed using deflate with the gzip wrapper, set        to “gzip”; otherwise, this header is not set)    -   If the request is for ./IS.sc?{%} where % is the character        sequence uniquely identifying the consolidated input, but no        electronic data object exists for that character sequence, the        programming code may let the Web server handle the request,        which may result in an HTTP status code of 404 (Not Found).    -   If the value retrieved from the Accept-Encoding header from the        client is “deflate” the electronic data object may be compressed        using deflate without the gzip wrapper (this may save 22 bytes        per response).    -   If the value retrieved from the Accept-Encoding header from the        client is “gzip” the electronic data object may be compressed        using deflate with the gzip wrapper.    -   It may send the electronic data object to the client by passing        the following headers:    -   Content-Type (Set to the appropriate value for the image format        [For example, GIF format is set to image/gif, JPEG format is set        to image/jpeg, and PNG format is set to image/png])    -   Last-Modified (Set to now's date and time minus one day)    -   Expires (Set to now's date and time plus one year)    -   Cache-Control (Set to public, max-age=31536000)    -   Content-Encoding (If the new response was compressed using        deflate without the gzip wrapper, set to “deflate”; if the new        response was compressed using deflate with the gzip wrapper, set        to “gzip”; otherwise, this header is not set)

More generally, embodiments may involve utilizing HTTP headerinformation from at least one of said request or said response, such asby a HTTP header information utilizer (811) responsive to at least oneof said client request or said server response. Utilizing HTTP headerinformation may involve the step of utilizing at least one headerselected from the group consisting of accept, accept-encoding,accept-charset, accept-language, cookie, host, referrer, user-agent, andx-forwarded-for, and the utilizer may be a utilizer utilizing theseheaders.

More generally, intermediating further may involve clearing the responseprovided by the server and providing a modified response to the clientcontaining information related to the accessed combined electronic dataobject, such as with a server response clearer (812) and a modifiedresponse creator (813) responsive to information related to the accessedcombined electronic data object. Such information may include headerinformation relevant to the provision of at least some of said combinedelectronic data object to said client, including perhaps a headerselected from the group consisting of content-encoding, content-type,and set-cookie.

More generally, intermediating further may involve receiving at leastone subsequent request from a client for at least some of the combinedelectronic data, such as by subsequent combined electronic data clientrequest receiver (814). The subsequent may be a request for CSS data,and intermediating may involve delivering the requested CSS data fromthe combined electronic data, such as by CSS data delivery system (815)responsive to said combined electronic data. Delivering may involveutilizing HTTP header information, such as by a HTTP header informationutilizer (816), wherein the HTTP header information may include a headerselected from the group consisting of content-type, last-modified,expires, cache-control, and content encoding, and the utilizer may beconfigured to utilize the same.

More generally, a subsequent request may be a request for script data,and a combined electronic data client request receiver (814) may be ascript data request receiver. Intermediating further may involvedelivering the requested script data from the combined electronic data,and an intermediary (806) may be a requested script data delivery systemresponsive to combined electronic data. Delivering may compriseutilizing HTTP header information, such as with an HTTP headerinformation utilizer (816), and the HTTP header information may includecontent-type, last-modified, expires, cache-control, and contentencoding, with the utilizer being configured to utilize the same.

More generally, a subsequent request may be a request for image data,and a combined electronic data client request receiver (814) may be animage data request receiver. Intermediating may involve delivering therequested image data from combined electronic data, and an intermediary(806) may be a requested image data delivery system responsive tocombined electronic data. Delivering may comprise utilizing HTTP headerinformation, such as with an HTTP header information utilizer (816), andthe HTTP header information may include content-type, last-modified,expires, cache-control, and content encoding, with the utilizer beingconfigured to utilize the same.

Embodiments may involve utilizing conventional infrastructure on atleast one other side of an electronic data exchange transaction. Stateddifferently, self-containing implementation on one side of an electronicdata exchange transaction may allow the rest of the electronic dataexchange transaction to proceed using conventional infrastructureelements. Accordingly, embodiments may include an electronic dataexchange transaction opposed side conventional infrastructureutilization architecture.

Embodiments therefore may be seen to allow operating externally from aconventional infrastructure, not changing a conventional infrastructure,intercepting data from a conventional infrastructure, utilizing aconventional server-client architecture, intercepting requests from aclient to a server, intercepting responses from a server to a client,installing software on a conventional server, utilizing a conventionalInternet transmission protocol, utilizing TCP, utilizing a conventionalInternet addressing protocol, utilizing IP, utilizing a conventionalInternet file transfer protocol, utilizing FTP, utilizing a conventionalInternet hypertext transfer protocol, utilizing HTTP, and utilizing anetworked environment, and may include architectures supporting thesame.

Embodiments may involve instructing at least one counterpart side of anelectronic data exchange transaction from the implementing side of thetransaction. This may follow from the fact of self-containment ofimplementation on one side of the transaction; however, it may beunderstood that wherein implementation of the method may require stepsat counterpart sides of the transaction, the counterpart participantsmay receive instructions for carrying out such steps from theimplementing participant to the transaction. Accordingly, embodimentsmay include an electronic data exchange transaction counterpart sideinstruction processor (817) at an implementing side of the architecture.

For example, in a server-client architecture, where a combinedelectronic data object may be stored at a server, the server mayinstruct the client by providing information relevant to the creation ofa combined electronic data indicator, such as may be associated to thecombined electronic data object. Such information may include, forexample, a character sequence that uniquely identifies the combinedelectronic object associated to the combined electronic data indicator,and may include HTTP header information, perhaps including alast-modified header, an expires header, and a cache-control header.Accordingly, embodiments may include a combined electronic dataindicator creation information provision processor (818), which invarious embodiments may be a processor responsive to a charactersequence that uniquely identifies a combined electronic data objectassociated to a combined electronic data indicator (819) and a processorresponsive to HTTP header information (820). Of course, this example maybe merely illustrative, and should not be construed to limit theunderlying principles only server-client or HTML embodiments.

Moreover, in various embodiments instructing may involve instructing aclient from a server, and perhaps instructing the client only to requestan electronic data object once. Accordingly, embodiments may include aclient-server architecture including perhaps a client single requestinstruction processor (821).

An example of instructing in one embodiment may be stated as follows:

-   -   If an addressed electronic data indicator is sent in output        similar to: ./CS.sc?{%}    -   Where % is a character sequence that uniquely identifies an        electronic data object, said client is instructed to only        request the electronic data object once from the server, even if        the same addressed electronic indicator is present in a        subsequent output to the client.    -   Those instructions may be sent by a server to a client by        passing the following headers when the electronic data object is        requested by the client:    -   Last-Modified (Set to now's date and time minus one day)    -   This header may instruct the client that the electronic data        object has not been modified since exactly 24 hours ago.    -   Expires (Set to now's date and time plus one year)    -   This header may instruct the client that the electronic data        object will not expire for one year, so it should not request        the electronic data object again for one year.    -   Cache-Control (Set to public, max-age=31536000)    -   This header may instruct the client that the electronic data        object will not expire for one year, so it should not request        the electronic data object again for one year.

Naturally, self-containing implementation on one side of an electronicdata exchange transaction may be implemented on any suitable side of anelectronic data exchange transaction, including perhaps implementing ona server side, implementing on a client side, or implementing on anintermediary side of a transaction, with architectures suitable tosupport the same.

Now with reference primarily to FIG. 9, an electronic data indicator invarious embodiments may be a pointer (901), and embodiments of theinventive technology may involve combining multiple pointers (901) intoa single combined pointer, such as with a single combined pointergenerator (902). Combining may be understood to involve takingindividual objects or indicators and integrating them into a form havingat least one unitary element. Pointers (901) may be described moregenerally elsewhere herein.

Moreover, in various embodiments, an electronic data object (909) may bea file, and embodiments may involve pointing to at least one such filewith a single combined pointer. For example, the single combined pointermay be in a Web page, or perhaps information on a client for loading aWeb page, and embodiments may involve providing the file to the Web pageusing the single combined pointer. Accordingly, embodiments may have asingle combined file pointer processor (903) responsive to a singlecombined pointer generator (902), wherein the processor may be a Webpage single combined file pointer processor, a Web page file provisionprocessor, or the like.

In various embodiments, providing a Web page may involve exchangingmultiple requests and responses between a server (907) and a client(906), and combining multiple pointers (901) into a single combinedpointer may involve reducing the number of such requests and responses.This may follow, for example, from the fact that the single combinedpointer may point to just one file, rather than multiple files stored atdisparate locations. Accordingly, embodiments may involve aclient-server multiple request and multiple response exchangearchitecture (905), and a single combined pointer generator (902) may bea request and response number reducer (908).

In various embodiments, requests and responses may include HTTP headerinformation, and embodiments may involve reducing the amount of suchHTTP header information by utilizing a single combined pointer to reducethe number of such headers utilized. Reducing may involve eliminating atleast 221 bytes per eliminated request header and eliminating at least126 bytes per eliminated response header in various embodiments.

Moreover, combining multiple pointers may involve eliminating up to 500bytes from the output, and a single combined pointer generator may be anup to 500 byte output elimination generator.

Now with reference primarily to FIG. 10, an electronic data object invarious embodiments may be a file (1001), and embodiments of theinventive technology may involve combining multiple files (1001) into asingle combined file (1002), such as with a single combined filegenerator (1003). Combining may be understood to involve takingindividual objects or indicators and integrating them into a form havingat least one unitary element. Files (1001) may be described moregenerally elsewhere herein.

Moreover, in various embodiments, an electronic data indicator (1005)may be a pointer, and embodiments may involve identifying a singlecombined file with a pointer, such as with a single combined fileindication processor (1004). For example, the single combined file maybe at a single combined file hosted on a server (1006), and embodimentsmay involve providing the file from the server to a client using asingle combined pointer, for example for the loading of a Web page.Accordingly, embodiments may have a single combined file indicationprocessor (1004) responsive to an electronic data indicator (1005),wherein the processor may be a file server provision processor (1007),and the file may be a server hosted file, such as a server hosted singlecombined file.

Moreover, in various embodiments combining files may result in sizesavings relative to the size of the uncombined files. For exampleembodiments may involve combining multiple files into a single combinedfile having a size of up to 52.3% less than the multiple files,combining multiple CSS files into a single combined CSS file having asize of up to 35.5% less than the multiple CSS files, combining multiplescript files into a single combined script file having a size of up to16.9% less than the multiple script files, combining multiple imagefiles into a single combined image file having a size of up to 34.8%less than the multiple image files. Accordingly, embodiments may includesingle combined file generators comprising reduced file size generatorscorresponding to the same.

Now with reference primarily to FIG. 11, embodiments of the inventivetechnology may involve eliminating redundant executable script from atleast one of a first location or a second location. Eliminatingredundant executable script may be understood to include removing scriptfrom programming code that may substantially duplicate, either instructure or function, script that already exists elsewhere in suchprogramming code. In various embodiments such executable script may bejavascript. Accordingly, embodiments may include a redundant executablescript eliminator (1102) at at least one of a first or second electronicstorage medium (1101), where such eliminator may be a javascriptredundant executable script eliminator.

An example of eliminating redundant executable script in one embodimentmay be stated as follows:

-   -   An inline script may look as follows:    -   <script type=“text/javascript”>        -   alert(‘Hello World!’);    -   </script>    -   In this case, the script element may be changed in output to a        function call referencing a variable declared in combined input:        <script type=“text/javascript”>eval(%);</script>    -   Where % is a unique character sequence.    -   The following variable declaration may be collocated to the        combined input: var %=‘$’;    -   Where % is said unique character sequence, and $ is the data        inside the script element. For this to evaluate to proper        JavaScript, occurrences in the data inside the script element of        the “\” character may have to be replaced with “\\”, occurrences        in the data inside the script element of the “′” character may        have to be replaced with “\′”, occurrences in said data inside        the script element of the “\n” line feed character may have to        be replaced with “\n\”, and occurrences in the data inside the        script element of the “\r” carriage return character may have to        be replaced with “\r\”.

More generally, embodiments may involve replacing programming codein-line script with a function call referencing a variable declaredelsewhere in the programming code.

Accordingly, embodiments may include a programming code in-line scriptreplacer (1103) responsive to a function call (1104) referencing avariable declared elsewhere in the programming code.

Some embodiments may involve providing a script on one page of amultiple page Web site, providing a function call on at least one otherpage of the multiple page Web site, and associating the function call tothe script. In this application, the function call may serve to take theplace of placing script on the other pages of the multiple-page Website, and it may be seen that redundant executable script may beeliminated. Accordingly, embodiments may include a first page scriptprovider (1105) responsive to a multiple page Web site, a function callprovider (1106) responsive to at least one other page of a multiple pageWeb site, and an association processor (1107) responsive to the scriptprovider (1105) and the function call provider (1106).

Of course, eliminating redundant executable script in variousembodiments may result in certain efficiencies. For example, replacingin-line script and providing a function call in various embodiments mayinvolve saving up to 2048 bytes. Accordingly, embodiments may involve anup to 2048 bytes replacer. Embodiments further may include an electronicdata transmitter (1108).

Now with reference primarily to FIG. 12, transmitting electronic data invarious embodiments may involve reducing transmission overhead.Transmission overhead generally may be understood to include theinfrastructure required to support transmitting electronic data, such asin an electronic data exchange transaction. In various embodiments, forexample reducing transmission overhead may involve reducing storagelocations for electronic data, reducing a number of electronic dataobjects, recuing a number of electronic data indicators, reducing anumber of electronic data exchange transactions, reducing a requiredelectronic data transmission bandwidth, and the like.

Accordingly, embodiments may include an electronic data transmitter(1201) and a transmission overhead reducer (1202), which in variousembodiments may include an electronic data storage location reducer, anelectronic data object number reducer, an electronic data indicatornumber reducer, an electronic data exchange transaction number reducer,a required electronic data transmission bandwidth reducer, and the like.

Moreover, in some embodiments reducing transmission overhead may resultin achieving effective compression, perhaps as described elsewhereherein, a transmission overhead reducer (1202) may be an effectivecompression achievement processor (1203).

Examples of reducing transmission overhead may include reducing HTTPheader information, such as perhaps by the use of combined electronicdata objects and combined electronic data indicators, and reducing HTMLtag information, such as perhaps by reducing the number of locationsthat may be specified by HTML tags. Accordingly, in various embodimentsan electronic data transmitter (1201) may be a reduced HTTP headerinformation transmitter, a reduced HTML tag information transmitter, orthe like.

Now with reference primarily to FIG. 13, embodiments may involve addingvarious methods described herein to an electronic communications network(1301). The term adding may be understood as including the given methodin the operation of such a network, perhaps as by complementing suchoperation, supplementing such operation, or the like. Accordingly,embodiments may include an electronic communications network interface(1302).

In some embodiments, adding may involve adding as a separable component(1303). A separable component (1303) may be understood to include acomponent that may be readily separated from the network. Examples mayinclude a modular component, an interchangeable component, or the like.Stated differently, adding as a separable component may involve addingthe subject method in such a manner that it does not become an integralpart of the network itself, but rather operates alongside of thenetwork, in conjunction with network, or the like.

Embodiments also may involve adding as a black box (1304). A black box(1304) may be understood to include devices, systems, objects, or thelike which may be viewed solely in terms of their input, output, andtransfer characteristics, without requiring knowledge or awareness oftheir internal workings. Stated differently, adding as a black box mayinvolve adding an element to a network that creates an additionalfunctionality for the network, requiring only input and output to andfrom the network, and not requiring the network to be aware of theinternal operations of the black box.

Embodiments may involve adding a method by plugging and playing, as byadding a plug and play component (1305). The term plugging and playingmay be understood to include adding to a network without requiringspecial technical support from the network, such as special connections,special hardware, special software, or the like. Stated differently,adding by plugging and playing may involve simply making a standardconnection, interface, or the like between the plug and play component(1305) and the network, and realizing the functionality of the plug andplay component (1305).

Moreover, in various embodiments adding may involve adding as hardware,software, adding at a server, adding at a client, adding as anintermediary, and the like, including perhaps any combination of theforegoing. Adding a method as herein described also may involveachieving effective compression of a step of transmitting electronicdata, perhaps also as elsewhere described herein. Accordingly,embodiments may include an electronic data exchange transactionintermediary (1306) and a transmission effective compression achievementprocessor (1307).

Now with reference primarily to FIG. 14, embodiments may involveautomatically minifying at least some programming code, such as by anautomated programming code minifier (1401). Automatically minifying mayinvolve executing with general applicability, which may be understood toinvolve accepting any supported programming code generally and providingthe automated minification capability. Accordingly, an automatedprogramming code minifier (1401) in various embodiments may be agenerally applicable execution automated programming code minifer.

In various embodiments, automatically minifying may involveautomatically minifying on a first request for given programming codeand storing the automatically minified programming code for subsequentrequests for such programming code. In this manner, certain efficienciesmay be achieved by avoiding unnecessarily repetitive minification ofprogramming code. Accordingly, embodiments may include a first requestautomated programming code minification processor (1402) and asubsequent request automatically minified programming code storageprocessor (1403).

Now with reference primarily to FIG. 15, combining in variousembodiments may involve executing programming code, such as with aprogramming code execution processor (1505) of a combiner (1501).

A first example of executing programming code may be stated as follows:

-   -   For a first case, an HTML element with the name “script” may        look as follows:    -   <script type=“text/javascript” src=“script.js”></script>    -   If the value for the “src” attribute refers to a resource that        can be read, the script element may be changed in output to:    -   <script type=“text/javascript”>eval(%);</script>    -   Where % is a unique character sequence.    -   The following may be collocated to consolidated input:    -   var %=‘$’;    -   Where % is a unique character sequence, and $ is the data read        from the value of the “src” attribute. For this to evaluate to        proper JavaScript, occurrences in data read from the value for        the “src” attribute of the “\” character may need to be replaced        with “\\”, occurrences in data read from the value for the “src”        attribute of the “′” character may need to be replaced with        “\′”, occurrences in data read from the value for the “src”        attribute of the “\n” line feed character may need to be        replaced with “\n\”, and occurrences in data read from the value        for the “src” attribute of the “\r” carriage return character        may need be replaced with “\r\”.    -   For a second case, an HTML element with the name “script” may        look as follows:    -   <script type=“text/javascript”>        -   alert(‘Hello World!’);    -   </script>    -   In this case, the script element may be changed in output to:    -   <script type=“text/javascript”>eval(%);</script>    -   Where % may be a unique character sequence.    -   The following may be collocated to consolidated input:    -   var %=‘$’;    -   Where % is a unique character sequence, and $ is the data inside        the script element. For this to evaluate to proper JavaScript,        occurrences in data inside the script element of the “\”        character may need to be replaced with “\\”, occurrences in said        data inside the script element of the “′” character may need to        be replaced with “\′”, occurrences in said data inside the        script element of the “\n” line feed character may need to be        replaced with “\n\”, and occurrences in said data inside the        script element of the “\r” carriage return character may need to        be replaced with “\r\”.    -   For a third case, two HTML elements with the name “img” may look        like this:    -   <img src=“image1.jpg” />    -   <img src=“image2.jpg” />    -   For each element, if the value for the “src” attribute refers to        a resource that can be read, the data read from the value of the        src attribute is collocated to a combined input, and the img        element may be changed in output to:    -   <img src=“./IS.sc ?{%1}” style=“background:url(IIS.sc ?{%2})%3px        %4px no-repeat;” />    -   <img src=“./IS.sc ?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;” />    -   Where %1 is a unique character sequence that identifies a clear        GIF image 1 pixel wide by 1 pixel high, %2 is a character        sequence that uniquely identifies the electronic data object at        the first location, %3 is the X coordinate of that image in the        combined input, and %4 is the Y coordinate of the image in the        consolidated input.    -   A second example of executing programming code may be stated as        follows:    -   For a first case, an HTML element with the name “link” may look        as follows:    -   <link href=“style.css” rel=“stylesheet” type=“text/css” />    -   If the value for the “href” attribute refers to a resource that        can be read, the entire link element may be removed from the        output, and the data read from the value for the “href”        attribute may be combined in the consolidated input.    -   For a second case, an HTML element with the name “style” may        look as follows:    -   <style type=“text/css”>        -   body {            -   font-family: Verdana;        -   }    -   </style>    -   The entire style element may be removed from the output, and the        data inside the style element may be combined in consolidated        input.    -   A third example of executing programming code may be stated as        follows:

For a first case, an input may contain one or more HTML elements withthe name “link,” each referring to a different location of electronicdata objects:

-   -   <link href=“style1.css” rel=“stylesheet” type=“text/css” />    -   <link href=“style2.css” rel=“stylesheet” type=“text/css” />    -   Where style1.css is the location of one electronic data object        and style2.css is the location of a second electronic data        object.    -   For each element, if the value for the “href” attribute refers        to a resource that can be read, the entire link element may be        removed from output, and the data read from the value for the        “href” attribute may be combined in consolidated input.    -   The consolidated input may be stored as an electronic data        object at a first location.    -   At the first location, a character sequence may be generated        that uniquely identifies the electronic data object at the first        location.    -   At the first location, the character sequence may be associated        to the electronic data object at the first location.    -   At the first location, use the character sequence to address an        electronic data indicator at a second location to the electronic        data object at the first location by adding the following to        output:    -   <link href=”./CS.sc?{%}” rel=“stylesheet” type=“text/css” />    -   Where % is said character sequence that uniquely identifies said        electronic data object at said first location.    -   In summary, two locations of electronic data objects:    -   <link href=“style1.css” rel=“stylesheet” type=“text/css” />    -   <link href=“style2.css” rel=“stylesheet” type=“text/css” />    -   . . . are replaced with one location of an electronic data        object:    -   <link href=“./CS.sc?{%}” rel=“stylesheet” type=“text/css” />    -   For a second case, input may contain one or more HTML elements        with the name “script,” each referring to a different location        of electronic data objects:    -   <script type=“text/javascript” src=“script1.js”></script>    -   <script type=“text/javascript” src=“script2.js”></script>    -   Where script1.js is the location of one electronic data object        and script2.js is the location of a second electronic data        object.    -   For each element, if the value for the “src” attribute refers to        a resource that can be read, the data read from the value of the        src attribute may be combined to consolidated input.    -   The consolidated input may be stored as an electronic data        object at a first location.    -   At the first location, a character sequence is generated that        uniquely identifies the electronic data object at the first        location.    -   At the first location, said character sequence is associated to        the electronic data object at the first location.    -   At the first location, use the character sequence to address the        electronic data indicator at the second location to the        electronic data object at said first location by adding the        following to said output:    -   <script type=“text/javascript” src=“./JS.sc?{%}”></script>    -   Where % is said character sequence that uniquely identifies said        electronic data object at said first location.    -   In summary, two locations of said electronic data objects:    -   <script type=“text/javascript” src=“script1.js”></script>    -   <script type=“text/javascript” src=“script2.js”></script>    -   . . . are replaced with one location of said electronic data        object:    -   <script type=“text/javascript” src=“./JS.sc?{%}”></script>    -   For a third case, input may contain one or more HTML elements        with the name “img,” each referring to a different location of        electronic data objects:    -   <img src=“image1.jpg” />    -   <img src=“image2.jpg” />    -   Where image1.jpg is the location of one electronic data object        and image2.jpg is the location of a second electronic data        object.    -   For each element, if the value for the “src” attribute refers to        a resource that can be read, the data read from the value of the        src attribute may be collocated to input.    -   The combined input may be stored as an electronic data object at        a first location.    -   At the first location, a character sequence is generated that        uniquely identifies the electronic data object at the first        location.    -   At the first location, the character sequence is associated to        the electronic data object at said first location.    -   At the first location, use said character sequence to address an        electronic data indicator at the second location to the        electronic data object at the first location by changing:    -   <img src=“image1.jpg” />    -   . . . to:    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2} %3px        %4px;” />    -   . . . and by changing:    -   <img src=“image2.jpg” />    -   . . . to:    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2} %3px        %4px;” />    -   Where %1 is a character sequence that uniquely identifies an        electronic data object at the first location that is a 1 pixel        wide by 1 pixel high transparent GIF image, %2 is the character        sequence that uniquely identifies the electronic data object at        the first location, %3 is the X coordinate of the image in said        electronic data object, and %4 is the Y coordinate of the image        in the electronic data object.    -   And where %1 and %2 are the same for each img element.    -   In summary, two locations of said electronic data objects:    -   <img src=“image1.jpg” />    -   <img src=“image2.jpg” />    -   . . . are replaced with one location of said electronic data        object:    -   <img src=“./IS.sc?{% 1}” style=“background:url(ITS.sc?{%2} %3px        % 4px;” />    -   <img src=“./IS.sc?{% 1}” style=“background:url(ITS.sc?{%2} %3px        % 4px;” />    -   A fourth example of executing programming code may be stated as        follows:    -   According to        https://developers.google.com/speed/articles/web-metrics, a Web        page refers to an average of 39.7 locations of said electronic        data objects (3.22 styles, 7.09 scripts, and 29.39 images) via        an average of 39.7 said electronic indicators.    -   Without this method, the input would contain 3.22 electronic        indicators for styles:    -   <link href=“style1.css” rel=” style sheet” type=“text/css” />    -   <link href=“style2.css” rel=” style sheet” type=“text/css” />    -   <link href=“style3.css” rel=” style sheet” type=“text/css” />    -   With this method, those three inputs can be combined, so they        are removed from said output, combined in said consolidated        input, and the following electronic indicator is added to said        output:    -   <link href=“./CS.sc?{%}” rel=“stylesheet” type=“text/css” />    -   Where % is said character sequence that uniquely identifies said        electronic data object at said first location.    -   In summary, three locations of said electronic indicators:    -   <link href=“style1.css” rel=“stylesheet” type=“text/css” />    -   <link href=“style2.css” rel=“stylesheet” type=“text/css” />    -   <link href=“style3.css” rel=“stylesheet” type=“text/css” />    -   . . . Are replaced with one location of said electronic        indicator:    -   <link href=“./CS.sc?{%}” rel=“stylesheet” type=“text/css” />    -   Without this method, the input would contain 7.09 electronic        indicators for scripts:    -   <script type=“text/javascript” src=“script1.js”></script>    -   <script type=“text/j avascript” src=“script2.js”></script>    -   <script type=”text/j avascript” src=“script3.js”></script>    -   <script type=”text/j avascript” src=“script4.js”></script>    -   <script type=”text/j avascript” src=“script5.js”></script>    -   <script type=”text/j avascript” src=“script6.js”></script>    -   <script type=”text/j avascript” src=“script7.js”></script>    -   With this method, those seven inputs can be collocated, so they        are mostly removed from said output and collocated to said        consolidated input, and the following electronic indicator is        added to said output:    -   <script type=”text/javascript” href=“./JS.sc?{%}”></script>    -   Where % is said character sequence that uniquely identifies said        electronic data object at said first location.    -   In summary, seven locations of said electronic indicators:    -   <script type=“text/javascript” src=“script1.js”></script>    -   <script type=“text/javascript” src=“script2.js”></script>    -   <script type=”text/j avascript” src=“script3.js”></script>    -   <script type=”text/javascript” src=“script4.js”></script>    -   <script type=“text/javascript” src=“script5.js”></script>    -   <script type=”text/javascript” src=“script6.js”></script>    -   <script type=”text/javascript” src=“script7.js”></script>    -   . . . Are replaced with one location of said electronic        indicator:    -   <script type=”text/javascript” href=“./JS.sc?{%}”></script>    -   Without this method, the input would contain 29.39 electronic        indicators for images:    -   <img src=“image1.jpg” />    -   <img src=“image2.jpg” />    -   <img src=“image3.jpg” />    -   <img src=“image4.jpg” />    -   <img src=“image5.jpg” />    -   <img src=“image6.jpg” />    -   <img src=“image7.jpg” />    -   <img src=“image8.jpg” />    -   <img src=“image9.jpg” />    -   <img src=“image10.jpg” />    -   <img src=“image11.jp g” />    -   <img src=“image12.jpg” />    -   <img src=“image13.jpg” />    -   <img src=“image14.jpg” />    -   <img src=“image15.jpg” />    -   <img src=“image16.jpg” />    -   <img src=“image17.jpg” />    -   <img src=“image18.jpg” />    -   <img src=“image19.jpg” />    -   <img src=“image20.jpg” />    -   <img src=“image21.jpg” />    -   <img src=“image22.jpg” />    -   <img src=“image23.jpg” />    -   <img src=“image24.jpg” />    -   <img src=“image25.jpg” />    -   <img src=“image26.jpg” />    -   <img src=“image27.jpg” />    -   <img src=“image28.jpg” />    -   <img src=“image29.jpg” />    -   With this method, those twenty-nine inputs can be collocated, so        they are mostly removed from said output and collocated to said        consolidated input, and their electronic indicators changed to        the following in said output:    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;” />    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;” />    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc ?{%2}) %3px        %4px no-repeat;” />    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>\    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;” />    -   <img src=“./IS.sc ?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;” />    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;” />    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;” />    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(./IS.sc?{%2}) %3px        %4px no-repeat;” />    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;” />    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;” />    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;” />    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;” />    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;” />    -   Where %1 is a character sequence that uniquely identifies an        electronic data object at a first location that is a 1 pixel        wide by 1 pixel high transparent GIF image, %2 is a character        sequence that uniquely identifies said electronic data object at        a first location, %3 is the X coordinate of the image in the        electronic data object, and %4 is the Y coordinate of the image        in the electronic data object.    -   And where %1 and %2 are the same for each img element.    -   In summary, twenty-nine locations of said electronic indicators:    -   <img src=“image1.jpg” />    -   <img src=“image2.jpg” />    -   <img src=“image3.jpg” />    -   <img src=“image4.jpg” />    -   <img src=“image5.jpg” />    -   <img src=“image6.jpg” />    -   <img src=“image7.jpg” />    -   <img src=“image8.jpg” />    -   <img src=“image9.jpg” />    -   <img src=“image10.jpg” />    -   <img src=“image 11.jpg” />    -   <img src=“image12.jpg” />    -   <img src=“image13.jpg” />    -   <img src=“image14.jpg” />    -   <img src=“image15.jpg” />    -   <img src=“image16.jpg” />    -   <img src=“image17.jpg” />    -   <img src=“image18.jpg” />    -   <img src=“image19.jpg” />    -   <img src=“image20.jpg” />    -   <img src=“image21.jpg” />    -   <img src=“image22.jpg” />    -   <img src=“image23.jpg” />    -   <img src=“image24.jpg” />    -   <img src=“image25.jpg” />    -   <img src=“image26.jpg” />    -   <img src=“image27.jpg” />    -   <img src=“image28.jpg” />    -   <img src=“image29.jpg” />    -   . . . Are replaced with one location of said electronic        indicator:    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;” />    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;” />    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;” />    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>\    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   <img src=“./IS.sc?{%1}” style=“background:url(IIS.sc?{%2}) %3px        %4px no-repeat;”/>    -   A fifth example of executing programming code may be stated as        follows:    -   When the following input is encountered:    -   <link href=” style.css” rel=“stylesheet” type=“text/css”/>    -   . . . If the value for the “href” attribute refers to a resource        that can be read, the data read from the value of the href        attribute may be contiguously combined in the consolidated CSS        input. By doing this sequentially, said second location may        exhibit the same behavior as if the input was not consolidated.    -   When the following input is encountered:    -   <style type=”text/css”>        -   body {            -   font-family: Verdana;        -   }    -   </style>    -   . . . The data inside the style element may be contiguously        combined in the consolidated CSS input. By doing this        sequentially, the second location may exhibit the same behavior        as if the input was not consolidated.    -   When the following input is encountered:    -   <script type=”text/javascript” src=“script.js”></script>    -   . . . If the value for the “src” attribute refers to a resource        that can be read, the data read from the value of the src        attribute may be contiguously combined in the consolidated        Javascript input as:    -   var %=‘$’;    -   Where % is said unique character sequence, and $ is the data        read from the value of the “src” attribute. For this to evaluate        to proper JavaScript, occurrences in data read from the value        for the “src” attribute of the “\” character may need to be        replaced with “\\”, occurrences in data read from the value for        the “src” attribute of the “′” character may need to be replaced        with “\′”, occurrences in data read from the value for the “src”        attribute of the “\n” line feed character may need to be        replaced with “\n\”, and occurrences in data read from the value        for the “src” attribute of the “\r” carriage return character        may need to be replaced with “\r\”.    -   By doing this sequentially, the second location may exhibit the        same behavior as if the input was not consolidated.    -   When the following input is encountered:    -   <script type=”text/javascript”>        -   alert(‘Hello World!’);    -   </script>    -   . . . The data inside the script element may be contiguously        combined in the consolidated Javascript input as:    -   var %=‘$’;    -   Where % is said unique character sequence, and $ is the data        inside the script element. For this to evaluate to proper        JavaScript, occurrences in data inside the script element of the        “\” character may need to be replaced with “\\”, occurrences in        data inside the script element of the “′” character may need to        be replaced with “\′”, occurrences in data inside the script        element of the “\n” line feed character may need to be replaced        with “\n\”, and occurrences in data inside the script element of        the “\r” carriage return character may need to be replaced with        “\r\”.    -   By doing this sequentially, the second location may exhibit the        same behavior as if the input was not consolidated.    -   When the following input is encountered:    -   <img src=”image.jpg” />    -   . . . If the value for the “src” attribute refers to a resource        that can be read, the data read from the value of the src        attribute may be hierarchically combined in the consolidated        image input.

More generally, embodiments may involve substituting at least onepreexisting programming code element referring to uncombined electronicdata with at least one substituted programming code element referring tocombined electronic data. Accordingly, embodiments may include apreexisting programming code element removal processor (1506) responsiveto an uncombined electronic data reference (1507) and a substitutedprogramming code element substitution processor (1508) responsive to acombined electronic data reference (1509). In various embodiments, apreexisting programming code element may include an HTML attributereferring to a resource that can be read, and the substitutedprogramming code element may be a unique character sequence identifyingthe resource as part of the combined electronic data. Embodimentsfurther may involve retrieving a resource from a location other than thelocation of the combined electronic data. Accordingly, embodiments mayinclude a combined electronic data resource retrieval processor (1510).

More generally, embodiments may involve removing a preexistingprogramming code element and incorporating a value for said preexistingprogramming code element into combined electronic data. Accordingly,embodiments may include a preexisting programming code element removalprocessor (1511) and a preexisting programming code element valueincorporation processor (1512) responsive to said combined electronicdata. Moreover, a preexisting programming code element in variousembodiments may be an HTML attribute referring to a resource that can beread. Embodiments further may involve avoiding requiring an initialrequest for said resource. Accordingly, embodiments may include aninitial request avoidance processor (1513).

Additionally, in various embodiments, combining may comprise collocatingwith a collector.

Embodiments also may involve retaining individual attributes of eachcombined element. This may include separately utilizing at least onesuch constituent element, perhaps such as utilizing at least oneelectronic data object individually. Utilizing further may involveretrieving an individual file. Accordingly, embodiments may include acombiner (1501), a constituent element separate utilization processor(1502), an individual electronic data object utilization processor(1503), and an individual file retrieval processor (1504).

Now with reference to FIGS. 1-19, various steps of transmittingelectronic data described herein may involve utilizing conventionalnetwork transmission elements. Such elements should be understood toinclude, but not be limited to TCP/IP, FTP, HTTP, client-serverarchitectures, the World Wide Web, networked environments, wire lineelements, wireless elements, mobile computing devices, and the like.Consistent with the principles described herein, the inventivetechnology may be capable of use with and may involve using an unalteredtransmission protocol, including but not limited to using unaltered TCP,using an unaltered addressing protocol, including but limited to usingunaltered IP, using an unaltered hypertext protocol, including but notlimited to using an unaltered HTTP, using an unaltered file transferprotocol, including but not limited to using unaltered FTP, and thelike.

With further reference to FIGS. 1-19, the methods and apparatusdescribed herein naturally may be implemented with any suitablehardware, software, hardware objects, software objects, servers,clients, intermediaries, or the like.

With further reference to FIGS. 1-19, as used herein throughout, theterm automated and its associated constructions may be understood toinclude having the capability of operating independently, perhaps suchas without substantial human intervention or supervision.

With further reference to FIGS. 1-19, the methods and apparatusdescribed herein may have particular suitability to loading of Web pagesamong servers and clients, wherein the client may have pointers pointingto information required for the Web page on the server, but of coursemay be more generally applicable to any suitable storage andtransmission of electronic data, and should not be construed to belimited simply to World Wide Web architectures.

As can be easily understood from the foregoing, the basic concepts ofthe present inventive technology may be embodied in a variety of ways.It involves both electronic data storage and transmission techniques aswell as devices to accomplish the appropriate electronic data storageand transmission. In this application, the electronic data storage andtransmission techniques are disclosed as part of the results shown to beachieved by the various devices described and as steps which areinherent to utilization. They are simply the natural result of utilizingthe devices as intended and described. In addition, while some devicesare disclosed, it should be understood that these not only accomplishcertain methods but also can be varied in a number of ways. Importantly,as to all of the foregoing, all of these facets should be understood tobe encompassed by this disclosure.

The discussion included in this patent application is intended to serveas a basic description. The reader should be aware that the specificdiscussion may not explicitly describe all embodiments possible; manyalternatives are implicit. It also may not fully explain the genericnature of the inventive technology and may not explicitly show how eachfeature or element can actually be representative of a broader functionor of a great variety of alternative or equivalent elements. Again,these are implicitly included in this disclosure. Where the inventivetechnology is described in device-oriented terminology, each element ofthe device implicitly performs a function. Apparatus claims may not onlybe included for the device described, but also method or process claimsmay be included to address the functions the inventive technology andeach element performs. Neither the description nor the terminology isintended to limit the scope of the claims that will be included in anysubsequent patent application.

It should also be understood that a variety of changes may be madewithout departing from the essence of the inventive technology. Suchchanges are also implicitly included in the description. They still fallwithin the scope of this inventive technology. A broad disclosureencompassing both the explicit embodiment(s) shown, the great variety ofimplicit alternative embodiments, and the broad methods or processes andthe like are encompassed by this disclosure and may be relied upon whendrafting the claims for any subsequent patent application. It should beunderstood that such language changes and broader or more detailedclaiming may be accomplished at a later date (such as by any requireddeadline) or in the event the applicant subsequently seeks a patentfiling based on this filing. With this understanding, the reader shouldbe aware that this disclosure is to be understood to support anysubsequently filed patent application that may seek examination of asbroad a base of claims as deemed within the applicant's right and may bedesigned to yield a patent covering numerous aspects of the inventivetechnology both independently and as an overall system.

Further, each of the various elements of the inventive technology andclaims may also be achieved in a variety of manners. Additionally, whenused or implied, an element is to be understood as encompassingindividual as well as plural structures that may or may not bephysically connected. This disclosure should be understood to encompasseach such variation, be it a variation of an embodiment of any apparatusembodiment, a method or process embodiment, or even merely a variationof any element of these. Particularly, it should be understood that asthe disclosure relates to elements of the inventive technology, thewords for each element may be expressed by equivalent apparatus terms ormethod terms—even if only the function or result is the same. Suchequivalent, broader, or even more generic terms should be considered tobe encompassed in the description of each element or action. Such termscan be substituted where desired to make explicit the implicitly broadcoverage to which this inventive technology is entitled. As but oneexample, it should be understood that all actions may be expressed as ameans for taking that action or as an element which causes that action.Similarly, each physical element disclosed should be understood toencompass a disclosure of the action which that physical elementfacilitates. Regarding this last aspect, as but one example, thedisclosure of a “transmitter” should be understood to encompassdisclosure of the act of “transmitting” —whether explicitly discussed ornot—and, conversely, were there effectively disclosure of the act of“transmitting”, such a disclosure should be understood to encompassdisclosure of a “transmitter” and even a “means for transmitting” Suchchanges and alternative terms are to be understood to be explicitlyincluded in the description. Further, each such means (whetherexplicitly so described or not) should be understood as encompassing allelements that can perform the given function, and all descriptions ofelements that perform a described function should be understood as anon-limiting example of means for performing that function.

Any patents, publications, or other references mentioned in thisapplication for patent are hereby incorporated by reference. Anypriority case(s) claimed by this application is hereby appended andhereby incorporated by reference. In addition, as to each term used itshould be understood that unless its utilization in this application isinconsistent with a broadly supporting interpretation, common dictionarydefinitions should be understood as incorporated for each term and alldefinitions, alternative terms, and synonyms such as contained in theRandom House Webster's Unabridged Dictionary, second edition are herebyincorporated by reference. Finally, all references listed in the list ofReferences To Be Incorporated By Reference or other informationstatement filed with the application are hereby appended and herebyincorporated by reference, however, as to each of the above, to theextent that such information or statements incorporated by referencemight be considered inconsistent with the patenting of this/theseinventive technology(s) such statements are expressly not to beconsidered as made by the applicant(s).

Thus, the applicant(s) should be understood to have support to claim andmake a statement of invention to at least: i) each of the electronicdata storage and transmission devices as herein disclosed and described,ii) the related methods disclosed and described, iii) similar,equivalent, and even implicit variations of each of these devices andmethods, iv) those alternative designs which accomplish each of thefunctions shown as are disclosed and described, v) those alternativedesigns and methods which accomplish each of the functions shown as areimplicit to accomplish that which is disclosed and described, vi) eachfeature, component, and step shown as separate and independentinventions, vii) the applications enhanced by the various systems orcomponents disclosed, viii) the resulting products produced by suchsystems or components, ix) each system, method, and element shown ordescribed as now applied to any specific field or devices mentioned, x)methods and apparatuses substantially as described hereinbefore and withreference to any of the accompanying examples, xi) an apparatus forperforming the methods described herein comprising means for performingthe steps, xii) the various combinations and permutations of each of theelements disclosed, xiii) each potentially dependent claim or concept asa dependency on each and every one of the independent claims or conceptspresented, and xiv) all inventions described herein.

In addition and as to computer aspects and each aspect amenable toprogramming or other electronic automation, the applicant(s) should beunderstood to have support to claim and make a statement of invention toat least: xv) processes performed with the aid of or on a computer,machine, or computing machine as described throughout the abovediscussion, xvi) a programmable apparatus as described throughout theabove discussion, xvii) a computer readable memory encoded with data todirect a computer comprising means or elements which function asdescribed throughout the above discussion, xviii) a computer, machine,or computing machine configured as herein disclosed and described, xix)individual or combined subroutines and programs as herein disclosed anddescribed, xx) a carrier medium carrying computer readable code forcontrol of a computer to carry out separately each and every individualand combined method described herein or in any claim, xxi) a computerprogram to perform separately each and every individual and combinedmethod disclosed, xxii) a computer program containing all and eachcombination of means for performing each and every individual andcombined step disclosed, xxiii) a storage medium storing each computerprogram disclosed, xxiv) a signal carrying a computer program disclosed,xxv) the related methods disclosed and described, xxvi) similar,equivalent, and even implicit variations of each of these systems andmethods, xxvii) those alternative designs which accomplish each of thefunctions shown as are disclosed and described, xxviii) thosealternative designs and methods which accomplish each of the functionsshown as are implicit to accomplish that which is disclosed anddescribed, xxix) each feature, component, and step shown as separate andindependent inventions, and xxx) the various combinations andpermutations of each of the above.

With regard to claims whether now or later presented for examination, itshould be understood that for practical reasons and so as to avoid greatexpansion of the examination burden, the applicant may at any timepresent only initial claims or perhaps only initial claims with onlyinitial dependencies. The office and any third persons interested inpotential scope of this or subsequent applications should understandthat broader claims may be presented at a later date in this case, in acase claiming the benefit of this case, or in any continuation in spiteof any preliminary amendments, other amendments, claim language, orarguments presented, thus throughout the pendency of any case there isno intention to disclaim or surrender any potential subject matter. Itshould be understood that if or when broader claims are presented, suchmay require that any relevant prior art that may have been considered atany prior time may need to be re-visited since it is possible that tothe extent any amendments, claim language, or arguments presented inthis or any subsequent application are considered as made to avoid suchprior art, such reasons may be eliminated by later presented claims orthe like. Both the examiner and any person otherwise interested inexisting or later potential coverage, or considering if there has at anytime been any possibility of an indication of disclaimer or surrender ofpotential coverage, should be aware that no such surrender or disclaimeris ever intended or ever exists in this or any subsequent application.Limitations such as arose in Hakim v. Cannon Avent Group, PLC, 479 F.3d1313 (Fed. Cir 2007), or the like are expressly not intended in this orany subsequent related matter. In addition, support should be understoodto exist to the degree required under new matter laws—including but notlimited to European Patent Convention Article 123(2) and United StatesPatent Law 35 USC 132 or other such laws—to permit the addition of anyof the various dependencies or other elements presented under oneindependent claim or concept as dependencies or elements under any otherindependent claim or concept. In drafting any claims at any time whetherin this application or in any subsequent application, it should also beunderstood that the applicant has intended to capture as full and broada scope of coverage as legally available. To the extent thatinsubstantial substitutes are made, to the extent that the applicant didnot in fact draft any claim so as to literally encompass any particularembodiment, and to the extent otherwise applicable, the applicant shouldnot be understood to have in any way intended to or actuallyrelinquished such coverage as the applicant simply may not have beenable to anticipate all eventualities; one skilled in the art, should notbe reasonably expected to have drafted a claim that would have literallyencompassed such alternative embodiments.

Further, if or when used, the use of the transitional phrase“comprising” is used to maintain the “open-end” claims herein, accordingto traditional claim interpretation. Thus, unless the context requiresotherwise, it should be understood that the term “comprise” orvariations such as “comprises” or “comprising”, are intended to implythe inclusion of a stated element or step or group of elements or stepsbut not the exclusion of any other element or step or group of elementsor steps. Such terms should be interpreted in their most expansive formso as to afford the applicant the broadest coverage legally permissible.The use of the phrase, “or any other claim” is used to provide supportfor any claim to be dependent on any other claim, such as anotherdependent claim, another independent claim, a previously listed claim, asubsequently listed claim, and the like. As one clarifying example, if aclaim were dependent “on claim 20 or any other claim” or the like, itcould be re-drafted as dependent on claim 1, claim 15, or even claim 25(if such were to exist) if desired and still fall with the disclosure.It should be understood that this phrase also provides support for anycombination of elements in the claims and even incorporates any desiredproper antecedent basis for certain claim combinations such as withcombinations of method, apparatus, process, and the like claims.

Finally, any claims set forth at any time are hereby incorporated byreference as part of this description of the inventive technology, andthe applicant expressly reserves the right to use all of or a portion ofsuch incorporated content of such claims as additional description tosupport any of or all of the claims or any element or component thereof,and the applicant further expressly reserves the right to move anyportion of or all of the incorporated content of such claims or anyelement or component thereof from the description into the claims orvice-versa as necessary to define the matter for which protection issought by this application or by any subsequent continuation, division,or continuation-in-part application thereof, or to obtain any benefitof, reduction in fees pursuant to, or to comply with the patent laws,rules, or regulations of any country or treaty, and such contentincorporated by reference shall survive during the entire pendency ofthis application including any subsequent continuation, division, orcontinuation-in-part application thereof or any reissue or extensionthereon.

What is claimed is:
 1. A method for transmitting electronic datacomprising the steps of: storing multiple data files at a server;storing multiple data pointers at a client; automatically identifying atleast one characteristic of each said data file relevant to a thresholdcriterion for combining said multiple data files; automaticallydetermining if said threshold criterion for combining said multiple datafiles has been satisfied; automatically combining said multiple datafiles into a single combined data file in accordance with said automaticdetermination if said threshold criterion; automatically combining saidmultiple data pointers into a single combined data pointer at saidclient; automatically associating said single combined data file at saidserver to said single combined data pointer at said client;automatically linking said server to said client via an electronic datacommunications network; automatically effectively compressing at leastone request from said client for at least one said data file at saidserver with said single combined pointer at said client; automaticallyeffectively compressing provision from said server of at least one saiddata file to said client with said single combined data pointer at saidclient; automatically transmitting said data file from said server tosaid client via said electronic data communications network at aneffective network transmission rate greater than a benchmark networktransmission rate for said electronic data communications network.
 2. Amethod for transmitting electronic data as described in claim 1 whereinsaid steps of automatically effectively compressing comprise the step ofleveraging a combination efficiency.
 3. A method for transmittingelectronic data as described in claim 1 wherein said steps ofautomatically effectively compressing comprise the step of using saiddata association to request and provide at least one said fileindividually.
 4. A method for transmitting electronic data as describedin claim 1 further comprising the step of self-containing implementationof said method on one side of an electronic data exchange transaction.5. A method for transmitting electronic data as described in claim 4wherein said step of self-containing implementation comprises the stepof avoiding counterpart implementation of said method on at least oneother side of said electronic data exchange transaction.
 6. A method fortransmitting electronic data as described in claim 4 wherein said stepof self-containing implementation comprises the step of instructing atleast one counterpart side of said electronic data exchange transactionfrom the implementing side of said electronic data exchange transaction.7. A method for transmitting electronic data as described in claim 1further comprising the step of eliminating redundant javascript at saidclient.
 8. A method for transmitting electronic data as described inclaim 1 further comprising the step of using said method with unalteredTCP/IP.
 9. A method for transmitting electronic data as described inclaim 1 further comprising the step of the step of retaining individualattributes of each said data file.
 10. A method for transmittingelectronic data as described in claim 1 wherein said step ofautomatically combining said multiple data files into a single combineddata file comprises the step of executing programming code.
 11. A methodfor transmitting electronic data as described in claim 10 wherein saidstep of executing programming code comprises the step of substituting atleast one preexisting programming code element referring to saidmultiple data files with at least one substituted programming codeelement referring to said single combined data file.
 12. A method fortransmitting electronic data as described in claim 11 wherein saidprogramming code comprises HTML programming code, wherein saidpreexisting programming code element comprises an HTML attributereferring to a resource that can be read, and wherein said substitutedprogramming code element comprises a unique character sequenceidentifying said resource as part of said combined data file.
 13. Amethod for transmitting electronic data as described in claim 12 furthercomprising the step of avoiding retrieving said resource from a locationother than said single combined data file.
 14. A method for transmittingelectronic data as described in claim 1 wherein said method comprisesthe step of reducing transmission overhead.
 15. A method fortransmitting electronic data as described in claim 14 wherein said stepof reducing transmission overhead comprises a step selected from thegroup consisting of reducing server storage locations for data files,reducing a number of data files, reducing a number of data pointers,reducing a number of electronic data exchange transactions, and reducinga required electronic data transmission bandwidth.
 16. An electronicdata transmission apparatus comprising: a server having multiple datafiles stored thereon; a client having multiple data pointers storedthereon; an automated threshold criterion combination characteristicidentifier responsive to said server; an automated threshold criteriondeterminer responsive to said automated threshold criterion combinationcharacteristic identifier; an automated data file combiner responsive tosaid automated threshold criterion determiner and to which said serverhaving multiple data files stored thereon is responsive; an automateddata pointer combiner to which said client having said multiple datapointers stored thereon is responsive; an automated data associatorresponsive to said automated data file combiner and said automated datapointer combiner; an electronic data communications network linking saidserver to said client; an automated data file request and provideeffective compressor responsive to said automated data associator and towhich said server having said multiple data files stored thereon andsaid client having said multiple data pointers stored thereon areresponsive; an automated data file transmission effective rate augmenterresponsive to a benchmark network transmission rate for said electronicdata communications network and to which said server, said client, andsaid electronic data communications network linking said server to saidclient are responsive.
 17. An electronic data transmission apparatus asdescribed in claim 16 wherein said automated data file request andprovide effective compressor comprises a combination efficiency leveragesystem.
 18. An electronic data transmission apparatus as described inclaim 16 wherein said automated data file request and provide effectivecompressor comprises an individual data file request and provisionsystem having an associated data processor.
 19. An electronic datatransmission apparatus as described in claim 16 further comprising aone-sided self-contained electronic data exchange transactionimplementation architecture.
 20. An electronic data transmissionapparatus as described in claim 19 wherein said one-sided self-containedelectronic data exchange transaction implementation architecturecomprises an electronic data exchange transaction opposed sidecounterpart implementation avoidance processor.
 21. An electronic datatransmission apparatus as described in claim 19 wherein said one-sidedself-contained electronic data exchange transaction implementationarchitecture comprises an electronic data exchange transactioncounterpart side instruction processor at said implementing side of saidarchitecture.
 22. An electronic data transmission apparatus as describedin claim 16 further comprising a redundant javascript eliminator at atleast one of said server or said client.
 23. An electronic datatransmission apparatus as described in claim 16 further comprising anelectronic data transmitter utilizing unaltered TCP/IP.
 24. Anelectronic data transmission apparatus as described in claim 16 whereinsaid automated data file combiner comprises a constituent data fileindividual attribute retention processor.
 25. An electronic datatransmission apparatus as described in claim 16 wherein said automateddata file combiner comprises a programming code execution processor. 26.An electronic data transmission apparatus as described in claim 25wherein said programming code execution processor comprises apreexisting programming code element removal processor responsive to anuncombined data file reference and a substituted programming codeelement substitution processor responsive to a combined data filereference.
 27. An electronic data transmission apparatus as described inclaim 26 wherein said programming code comprises HTML programming code,wherein said preexisting programming code element comprises an HTMLattribute referring to a resource that can be read, and wherein saidsubstituted programming code element comprises a unique charactersequence identifying said resource as part of said combined data file.28. An electronic data transmission apparatus as described in claim 27further comprising a combined data file resource retrieval processor.29. An electronic data transmission apparatus as described in claim 16wherein said apparatus comprises a transmission overhead reducer.
 30. Anelectronic data transmission apparatus as described in claim 29 whereinsaid transmission overhead reducer comprises a reducer selected from thegroup consisting of a server storage location reducer, an data filenumber reducer, a data pointer reducer, an electronic data exchangetransaction number reducer, and a required electronic data transmissionbandwidth reducer.